ci: grant the CLI build job permission to upload release assets - #263
Merged
Conversation
Attaching the built binaries failed with "HTTP 403: Resource not accessible by integration". The job uploads through GITHUB_TOKEN but declares no permissions block, so it inherits the default — and the default here is read-only. Grant `contents: write` on that job alone rather than raising the default for every workflow, so the elevated permission is scoped to the step that needs it.
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 v0.8.5 release published to crates.io successfully, but all three
Build CLIjobs failed at the upload step withHTTP 403: Resource not accessible by integration, so no binaries are attached to that release.The job uploads through
GITHUB_TOKENbut declares nopermissionsblock, so it inherits the default workflow permission — which is read-only here. Grantingcontents: writeon that job alone keeps the elevated permission scoped to the step that needs it, rather than raising the default for every workflow.