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

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

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

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

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

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

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

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

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

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

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

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

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

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

#tdesktop