Skip to content

Use a repo-scoped PAT for the release token - #6

Merged
lorenzocamilli merged 1 commit into
mainfrom
fix/release-pat
Aug 16, 2026
Merged

Use a repo-scoped PAT for the release token#6
lorenzocamilli merged 1 commit into
mainfrom
fix/release-pat

Conversation

@lorenzocamilli

Copy link
Copy Markdown
Contributor

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.

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.
@lorenzocamilli
lorenzocamilli merged commit f9a1e85 into main Aug 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant