Skip to content

ci: declare the token permissions of the release job - #5

Merged
kylecarbs merged 1 commit into
mainfrom
ci/declare-release-token-permissions
Nov 17, 2026
Merged

kylecarbs merged 1 commit into
mainfrom
ci/declare-release-token-permissions

Conversation

@kylecarbs

Copy link
Copy Markdown
Member

The tag job in .github/workflows/release.yaml writes with GITHUB_TOKEN but declares no permissions:, so it relies on the org's default token permission being write. The org is moving that default to read, and this job would fail on its next release. This gives it contents: write. Nothing changes while the default is still write.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kylecarbs
kylecarbs merged commit 12d2382 into main Nov 17, 2026
2 of 4 checks passed
@kylecarbs
kylecarbs deleted the ci/declare-release-token-permissions branch November 17, 2026 00:26
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.

2 participants