Repository navigation
fix(release): grant actions:read so preflight can see pr.yml - #53
Merged
Merged
Conversation
The workflow-level permissions block only listed contents/id-token, which implicitly set actions to none. gh run list then returned nothing, the 2>/dev/null swallowed the error, and preflight spun out its 5-minute timeout even though pr.yml had already finished green. - add actions: read to the permissions block - drop 2>/dev/null so future gh failures are visible in the log
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
preflightwith a 5-minute timeout waiting forpr.yml, even thoughpr.ymlon the same commit had already completed green at 12:53:34Z.permissions:block listed onlycontents: writeandid-token: write. Specifying any scope implicitly sets every other scope tonone, soactionswasnone,gh run listreturned empty, and2>/dev/null || trueswallowed the underlying error. The poll loop never sawcompleted.actions: readto the permissions block, and drop2>/dev/nullso futuregherrors are visible in the log.Test plan
releaseagainstmain(testpypi target) oncepr.ymlis green — preflight should now detect the green run and advance tobuild.