Skip to content

ci: declare GITHUB_TOKEN permissions (org default is now read) - #509

Open
shuluster wants to merge 1 commit into
mainfrom
ci/explicit-token-permissions
Open

shuluster wants to merge 1 commit into
mainfrom
ci/explicit-token-permissions

Conversation

@shuluster

Copy link
Copy Markdown
Contributor

Why

The loop-payments org default for GITHUB_TOKEN changed from write to read on 2026-09-10 (follow-up to GitHub's fork-PR workflow-policy notice GH-1009062-8224-a). Jobs that write through the token now need an explicit permissions: block, or they fail with Resource not accessible by integration.

What

Adds a job-level permissions: block to:

  • .github/workflows/release.yml :: release → contents: write — creates a GitHub release with actions/create-release

Explicit blocks override the org default; nothing else changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Sc5PkPbFxTYVzdKvVjZhBY

The org default for GITHUB_TOKEN changed from write to read on 2026-09-10.
This job creates a GitHub release with actions/create-release, so without an explicit permissions block it now fails with
"Resource not accessible by integration".

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Sc5PkPbFxTYVzdKvVjZhBY
@shuluster
shuluster enabled auto-merge (squash) September 11, 2026 02:35
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