Repository navigation
Fix immutable tag history in release clipboard qualification - #8
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
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.
The release clipboard job checked out only the source commit, leaving the immutable tag ref unavailable. RC3 therefore refused source admission before either browser ran.
Fetch full history in that job, matching the candidate and publish jobs. Keep exact tag/main/source validation, artifact binding and dependent protected publication unchanged. Add a real Git missing-tag regression and a contract covering all three checkout jobs.
Validation: all 21 editor-release tests pass; the new contract fails on the previous workflow. Independent review found no blocking issues. RC3 remains immutable; the corrected workflow will build a new RC4 candidate.