fix(release): preflight the release branch namespace before createRef - #13
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.
Found on QuickAdd's first prepare run: a stale branch literally named
release(a stray semantic-release version commit from 2025) makes creatingrelease/x.y.zimpossible - git cannot hold bothrefs/heads/releaseandrefs/heads/release/*- and the failure surfaces as a bareHttpError: Reference update failed(422) from POST /git/refs, which is deterministic but completely opaque.The open-pr step now preflights the namespace before creating any git objects: it lists
heads/releasematching refs and fails with an actionable message ("delete or rename the 'release' branch") when the exact bare ref exists. Detection useslistMatchingRefswith an exact-match filter rather thangetRef, which is ambiguous on prefix collisions.The same preflight for
release-run/<version>recovery branches in the validate stage lands with the validate rewrite PR in this stack, along with the README migration-checklist note.Fixes #10