You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7add838
Browse filesBrowse the repository at this point in the historyBrowse files
feat(desktop): version canary builds by run number and build stable only from main (#434)
* feat(desktop): version canary builds by run number and build stable only from main
Canary's bundle version is now <package version>.<workflow run number>, so it
can ship patch builds without a package bump; its shown version is
<package version>+<sha7> in About Ace, Settings, and the GitHub release name.
Tags, archives, and feed entries use the bundle version. Stable keeps plain
x.y.z. The publisher compares versions with Sparkle's numeric order.
The release workflow refuses a stable revision that main does not contain, and
`bun desktop ci stable` dispatches on main to match the environment.
Why: apps/desktop/scripts/version.ts#function version | bundle versions must stay strictly increasing per channel because Sparkle orders updates by CFBundleVersion alone; the SHA is display-only and the canary build number must exceed every published canary's
Why: apps/desktop/scripts/version.ts#function order | must match Sparkle's comparator: a longer numeric version is newer when shared parts match, so 0.0.46.N follows the three-part canaries
Why: .github/workflows/desktop-release.yml | stable must build only revisions main contains; the environment's branch rule alone does not cover the revision input
* lane: sync release-versions memory
bundle versions must stay strictly increasing per channel because Sparkle orders updates by CFBundleVersion alone; the SHA is display-only and the canary build number must exceed every published canary's
0 commit comments