Skip to content

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

Merged
shuluster merged 2 commits into
mainfrom
ci/explicit-token-permissions
Sep 11, 2026
Merged

shuluster merged 2 commits 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-if-new-version.yml :: maybe-release → contents: write — calls the reusable release.yml, which creates a GitHub release; a called workflow cannot exceed the caller's permissions
  • .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

shuluster and others added 2 commits September 10, 2026 18:04
The org default for GITHUB_TOKEN changed from write to read on 2026-09-10.
This job calls the reusable release.yml, which creates a GitHub release; a called workflow cannot exceed the caller's permissions, 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
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 merged commit 7aa8ad2 into main Sep 11, 2026
1 check passed
@shuluster
shuluster deleted the ci/explicit-token-permissions branch September 11, 2026 01:59
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