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

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

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

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

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

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

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

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

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

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

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

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

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

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

#tdesktop