telegramdesktop/tdesktop/public-canary • 7cc0979 • 2 files, +821/-0 Add focused tests for v2 update

telegramdesktop/tdesktop/public-canary • 7cc0979 • 2 files, +821/-0
Add focused tests for v2 update verification

telegramdesktop/tdesktop/public-canary • 1b740e3 • 1 files, +862/-0
Add canary build and publish workflow

telegramdesktop/tdesktop/public-canary • 30ebc87 • 1 files, +186/-163
Build one canary lane per repository in CI

telegramdesktop/tdesktop/public-canary • bc3526f • 3 files, +31/-13
Use readable v2 update file names

telegramdesktop/tdesktop/public-canary • 31f96ca • 4 files, +117/-8
Use new update names and pinned Bot API image in CI

telegramdesktop/tdesktop/public-canary • 46bc5df • 3 files, +108/-62
Ship per-arch mac updates with a universal installer

telegramdesktop/tdesktop/public-canary • 4317bc5 • 1 files, +70/-28
Publish portable archives as canary first installs

telegramdesktop/tdesktop/public-canary • 3c9acb9 • 1 files, +5/-4
Drop the bundled d3d compiler from canary builds

telegramdesktop/tdesktop/public-canary • 9bd400c • 3 files, +41/-4
Embed external and local signatures in one packer pass

telegramdesktop/tdesktop/public-canary • cff50c2 • 2 files, +82/-3
Add a v2 update switch to the release build scripts

telegramdesktop/tdesktop/public-canary • 4b87718 • 1 files, +29/-1
Read the pinned metadata through the local Bot API

telegramdesktop/tdesktop/public-canary • 1b4d58f • 3 files, +25/-1
Support v2 updates in the updater and deploy scripts

telegramdesktop/tdesktop/public-canary • 9c32fc4 • 23 files, +872/-216
Harden canary builds running.

#tdesktop