ci: verify release ancestry before privileged jobs - #15
Merged
Conversation
morrow-bluedot
approved these changes
Aug 31, 2026
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.
Summary
contents: readtag-verification job before any release job receives write or OIDC authoritySecurity rationale
The existing workflow checked tag identity and main ancestry only after GitHub had already issued a write/OIDC-capable job token and checkout had persisted its credential. This change moves the trust decision ahead of privileged-token issuance.
Verification
Exact head:
f05a0ca1b1ecbefc7020442344024b204632d099git diff --check: passedNo tag or release is created by this PR.