Repository navigation
fix(release): let the release workflow inherit the caller's permissions - #64
Merged
Merged
Conversation
The top-level permissions block capped GITHUB_TOKEN and set actions to none, so the Version Packages PR CI dispatch failed with 403 even when the caller granted actions: write. Without the block the job inherits the caller's grant. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: unional <homawong@gmail.com>
|
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
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 CI dispatch step added for the Version Packages PR fails with
HTTP 403: Resource not accessible by integration(cyberuni/iso-error, release run 38112276866), even though the caller's release job grantsactions: write.The cause is this reusable workflow's own top-level
permissions:block (id-token,contents,pull-requests). It caps the token, so every scope it omits,actionsincluded, becomesnone. Addingactions: writeto the block would break every caller that does not grant it, because a called workflow may not request more than its caller grants.This removes the block, so the job inherits exactly what the caller grants. A reusable workflow can never exceed its caller's grant, so existing callers lose nothing: those that grant
id-token,contentsandpull-requestskeep working, and those that also grantactions: writeget CI on the Version Packages PR. The header now says what callers must grant and that the workflow declares no permissions of its own.Verified with actionlint.
🤖 Generated with Claude Code