-
Notifications
You must be signed in to change notification settings - Fork 3k
fix(desktop): harden release pipeline #9009
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
7921ae2
a1f78f7
895ca61
d82a9e5
ccd67e2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| # Desktop release hardening | ||
|
|
||
| The Desktop release should preserve the last complete bundled runtime until a replacement is fully assembled, recover that runtime on the next run if a swap is interrupted, reuse a Node.js archive verified against a fresh official checksum, and publish only installer/updater artifacts. Published prereleases must use a SemVer prerelease suffix so a later stable build has a strictly newer updater version. | ||
|
|
||
| Stable releases continue to mirror versioned assets to Aliyun OSS before advancing the OSS latest manifest. A normal release run now fails if the GitHub stable feed does not match the version it just published; manual backfills of older releases still leave the latest feed unchanged. | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [P2] Keep the design contract aligned with the newer-feed branch This says a normal release fails whenever the GitHub stable feed differs from the version it just published, but the implemented contract intentionally succeeds when the current feed is strictly newer (and the PR description now says so). Could we qualify this as failing only when the feed is invalid or older, while preserving a newer feed? Otherwise the design note tells a future maintainer to undo the intended behavior. |
||
|
|
||
| Verification covers the release workflow contracts, the Desktop release helpers, runtime smoke checks, and a dry-run installer build. | ||
Uh oh!
There was an error while loading. Please reload this page.