Repository navigation
fix(ci): grant contents write to the release job - #227
Open
nijeesh-stream wants to merge 1 commit into
Open
nijeesh-stream wants to merge 1 commit into
nijeesh-stream wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nijeesh-stream
requested review from
JimmyPettersson85,
shaljam and
vishalnarkhede
as code owners
October 29, 2026 13:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Release workflow creates the tag and GitHub release with
GITHUB_TOKEN, but #219 pinned the workflow tocontents: read. The v3.27.0 release run published the gem, then failed onCreate release on GitHubwithError 403: Resource not accessible by integration(run). I created the v3.27.0 GitHub release by hand.Solution
contents: writeon the Release workflow, the minimumncipollo/release-actionneeds to push a tag and create a release.pull-requestsstays read-only. Same fix as GetStream/stream-chat-go#400.How to verify
Next
release-*PR merge: theCreate release on GitHubstep 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: writeon the Release workflow’s defaultGITHUB_TOKENpermissions so mergedrelease-*PRs can finish the GitHub release step again.That permission is required for
ncipollo/release-actionto push the version tag and create the release; withcontents: read(from #219),Create release on GitHubfailed with 403 Resource not accessible by integration after the gem publish succeeded.pull-requests: readis unchanged.Reviewed by Cursor Bugbot for commit db38716. Bugbot is set up for automated code reviews on this repo. Configure here.