ci: add one-shot Desktop v0.5.5 tag recovery - #4806
Closed
wesbillman wants to merge 1 commit into
Closed
Conversation
Add an owner-only manual recovery for the already merged and validated 0.5.5 candidate. Recheck the immutable PR, Git graph, payload, CI, and existing tag before allowing the release-tagger App to create the tag. Co-authored-by: Carl <c7ebe626f000404285d3686e1dc74cc07cc60a9754a150041ba132e14bd3e2ec@buzz.block.builderlab.xyz> Signed-off-by: Wes <wesbillman@users.noreply.github.com>
Collaborator
Author
|
Closing because the release owner chose the revert-and-regenerate recovery path instead. This one-shot workflow is no longer needed. |
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.
Summary
Add a one-shot, owner-dispatched recovery workflow for the already merged Desktop
0.5.5release candidate.The workflow is bound to:
4a2305170eef565bf1836e2859247e67c030f8af2d03d37b05b68186b2caad9da79080032be3ac72a0ed13de14ee64dd90c32335790f7d3b4e94330ddesktop-v0.5.5wesbillmandispatch frommainwith an exact confirmation phraseBefore minting the release-tagger token, it revalidates PR identity, Git graph, candidate/squash tree equality, reachability from
main, release metadata/payload, every required candidate check, and combined commit status. Tag creation is immutable/idempotent and refuses an existing conflicting tag.This recovers run 30958500645, which failed only because #4800 had no exact-head approval before merge. It does not weaken the existing auto-tag flow or repository tag protection.
Validation
ruby -e 'require "yaml"; YAML.parse_file(ARGV.fetch(0))' .github/workflows/recover-desktop-v0.5.5.ymlbash scripts/test-release-ref-contract.shgit diff --check origin/main...HEADbranch-skewhook