Use a repo-scoped PAT for the release token - #6
Merged
Conversation
The org's Actions settings lock default GITHUB_TOKEN permissions to read-only for this repo, with no repo-level override available (the "Read and write permissions" radio is disabled in the repo's own settings) — so the contents:write job permission added in the previous commit isn't sufficient by itself. Point action-gh-release at a RELEASE_TOKEN secret (a fine-grained PAT scoped to just this repo, Contents: Read and write) instead.
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.
The org's Actions settings lock default GITHUB_TOKEN permissions to read-only for this repo, with no repo-level override available (the "Read and write permissions" radio is disabled in the repo's own settings) — so the contents:write job permission added in the previous commit isn't sufficient by itself. Point action-gh-release at a RELEASE_TOKEN secret (a fine-grained PAT scoped to just this repo, Contents: Read and write) instead.