Canary 1.51.1+canary.b04eb10f
Pre-releaseCanary 1.51.1+canary.b04eb10f
This is not the release you want unless you came here to test one. It is built from
main automatically, it is unsigned on Windows, and it is replaced in place every time
main moves — the Latest release is the stable download.
Downloads
| Platform | File | Built from | Run | Attached |
|---|---|---|---|---|
| linux-arm64 | canary-linux-arm64-dev-3.0-canary.tar.zst |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| linux-x64 | canary-linux-x64-dev-3.0-canary.tar.zst |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| macos-arm64 | canary-macos-arm64-dev-3.0-canary.app.tar.zst |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| macos-arm64 | canary-macos-arm64-dev-3.0.dmg |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| macos-x64 | canary-macos-x64-dev-3.0-canary.app.tar.zst |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| macos-x64 | canary-macos-x64-dev-3.0.dmg |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| win-x64 | canary-win-x64-dev-3.0-canary.zip |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| cli-linux-arm64 | dev3-cli-linux-arm64.tar.gz |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| cli-linux-x64 | dev3-cli-linux-x64.tar.gz |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| cli-macos-arm64 | dev3-cli-macos-arm64.tar.gz |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
| cli-macos-x64 | dev3-cli-macos-x64.tar.gz |
b04eb10f0 |
33620318403 | 2026-09-02T10:54:52.659Z |
Each row names the RUN that produced those exact bytes, not just the commit: Windows
trees are not byte-reproducible, and a run only rebuilds the platforms whose feed is
behind, so rows can legitimately come from different commits.
Windows
The zip is the tree a CI job actually launched and shut down cleanly. It is unsigned,
so the first launch shows SmartScreen's warning — that is the missing certificate, not a
malware verdict. Extract it with Explorer and run the executable inside; there is nothing
to install.
Sent here by the app's own refusal?
Switching stable → canary in place only works on macOS: everywhere else the running app
IS the channel folder, so an in-place switch would install into a directory the launcher
never starts, and the updater refuses instead of silently doing nothing. Its message says
to install the other channel's build from the releases page — that is this page, and the
file is the one on the win-x64 row above. Once it is running, canary updates itself
inside the canary channel on macOS and Linux; on Windows in-place updating is not reliable
yet, so download the win-x64 zip from this page again to move to a newer canary.
Updates do not come from this page
The in-app updater reads the canary feed in S3 and orders builds by buildOrder, never by
a version string or a GitHub release. This page is a download surface for people; deleting
it would not affect a single client.
Rendered 2026-09-02T10:54:52.659Z · tag canary is moved to the newest published commit on every publish.