Skip to content

fix(ci): grant contents write to the release job - #227

Open
nijeesh-stream wants to merge 1 commit into
masterfrom
fix/release-contents-write
Open

nijeesh-stream wants to merge 1 commit into
masterfrom
fix/release-contents-write

Conversation

@nijeesh-stream

@nijeesh-stream nijeesh-stream commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Problem

The Release workflow creates the tag and GitHub release with GITHUB_TOKEN, but #219 pinned the workflow to contents: read. The v3.27.0 release run published the gem, then failed on Create release on GitHub with Error 403: Resource not accessible by integration (run). I created the v3.27.0 GitHub release by hand.

Solution

contents: write on the Release workflow, the minimum ncipollo/release-action needs to push a tag and create a release. pull-requests stays read-only. Same fix as GetStream/stream-chat-go#400.

How to verify

Next release-* PR merge: the Create release on GitHub step passes and the tag appears under Releases.

🤖 Generated with Claude Code


Note

Low Risk
CI-only permission change for release automation; no application or runtime behavior changes.

Overview
Restores contents: write on the Release workflow’s default GITHUB_TOKEN permissions so merged release-* PRs can finish the GitHub release step again.

That permission is required for ncipollo/release-action to push the version tag and create the release; with contents: read (from #219), Create release on GitHub failed with 403 Resource not accessible by integration after the gem publish succeeded. pull-requests: read is unchanged.

Reviewed by Cursor Bugbot for commit db38716. Bugbot is set up for automated code reviews on this repo. Configure here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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