Release: grant actions: read to the shared-workflow caller - #47
Merged
Conversation
The shared release pipeline declares `actions: read`, which it uses to read this caller`s environment protection. A calling job that pins contents/id-token/pull-requests and nothing else grants `actions: none`, and a called workflow may only downgrade the caller`s token, never escalate it, so GitHub refused the whole workflow at startup: 1s, no jobs, no logs, and no refusal printed anywhere. The shared file states the precondition in its own header, that callers be granted this FIRST and the file adopted second; it was adopted the other way round and every Release in the fleet has been failing at startup since.
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.
The shared release pipeline declares
actions: read, which it uses to read this caller's environment protection. A calling job that pins contents/id-token/pull-requests and nothing else grantsactions: none, and a called workflow may only downgrade the caller's token, never escalate it, so GitHub refused the whole workflow at startup: 1s, no jobs, no logs, no refusal printed.The shared file states the precondition in its own header: grant callers this FIRST, adopt the file second. It was done the other way round, so every
Releasein the fleet has been failing atstartup_failuresince. Found byjust ci-sweepon the umbrella, which now reports default-branch CI per workflow.One line, workflow-only. No source, test or package change.