fix(ci): grant contents: write in main-build.yml#1092
Merged
cjpais merged 1 commit intocjpais:mainfrom Mar 19, 2026
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
2 participants
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.
Before Submitting This PR
Human Written Description
The main-build.yml I added in #1091 has a startup_failure on first run. GitHub enforces that when a calling workflow job specifies permissions, those permissions must be >= what the called reusable workflow declares — build.yml declares contents: write, so the caller must also grant contents: write or GitHub won't start the jobs at all. Missed this during local testing since actionlint doesn't catch it.
Related Issues/Discussions
Fixes startup_failure introduced by #1091
Testing
AI Assistance
AI was used
Tools used: Claude Code
How extensively: identified and fixed the permissions mismatch