fix(ci): grant build-phar caller permission to fix release-please startup failure#37
Merged
Merged
Conversation
Workflow-level permissions:{} means the build-phar caller-job inherited
no permissions. The local reusable workflow build-phar.yml declares
permissions: contents: write at workflow level. GitHub rejects the call
at startup because the caller cannot grant permissions it doesn't have,
producing STARTUP_FAILURE with no logs (run 25553201816).
Adding permissions: contents: write at the build-phar caller-job level
gives it permission to grant to the called reusable workflow.
Assisted-by: Claude Code
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.
Summary
Fixes startup failure on the Release Please workflow (run 25553201816) introduced by #28.
The workflow has
permissions: {}at the top level. Thebuild-pharcaller-job had nopermissions:block of its own, so it inherited empty permissions. The local reusable workflowbuild-phar.ymldeclarespermissions: contents: writeat workflow level. GitHub rejects the call at startup because the caller cannot grant permissions it doesn't have, producingSTARTUP_FAILUREwith no logs.Adding
permissions: contents: writeat thebuild-pharcaller-job level gives it permission to grant to the called workflow.The
release-pleasejob already has its ownpermissions:block, so it wasn't affected.Test plan