Repository navigation
Fix immutable-release preflight permission boundary - #2
Merged
Merged
Conversation
Author
|
Retriggering the pull_request event because GitHub did not create check suites for the initial opened event. |
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
The v0.0.1 tag build stopped before signing because GitHub documents the immutable-releases settings endpoint as requiring repository Administration read permission. A workflow GITHUB_TOKEN cannot receive that permission, so the endpoint returned 403 Resource not accessible by integration.
Keep the actual security boundary explicit:
Validation