Repository navigation
ci: publish verified Mac packages before full release - #3416
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ready Mac installers currently cannot join a partial Desktop release until the other Mac architecture finishes. Add a single-platform mode to
Publish Ready Desktop Assetsso a verified Mac producer can publish its DMG and updater archive, with both detached signatures.The publisher requires successful Prepare and Package jobs, an unexpired normal bundle, the original tag and protected-main history, and the existing release public key. It verifies both signatures, preserves existing bytes and signatures on retries, and reads every uploaded file back. It leaves release notes, Latest and update feeds unchanged; the complete Desktop publisher retains its full-platform gate.
Validation:
pnpm run check:github-config(51 passed, one existing PowerShell skip), including rejection of failed, expired, duplicate, wrong-platform and untrusted sources; completed-release refusal; and retry signature reuse only for identical payload bytes. No product/runtime changes or remote-scenario claims.