Repository navigation
Give the release workflow permission to create GitHub releases - #2916
Merged
Merged
Conversation
The release workflow's "Publish GitHub Release" step (ncipollo/release-action) creates a GitHub release with the generated notes, which needs contents: write. The job only had contents: read, so the step failed with "Error 403: Resource not accessible by integration" on every release since 4.0.0.dev5. The earlier steps, including publishing to PyPI, succeeded each time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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 (
.github/workflows/release.yml) never runs all the way through. Its last step, Publish GitHub Release (ncipollo/release-action), creates a GitHub release with the generated release notes. That needscontents: write, but the job only hadcontents: read, so the step fails with:Every release run in the Actions history since 4.0.0.dev5 failed this way, including dev6, dev7 and dev8; the latest is run 37360674136. Every earlier step succeeded each time: build, publish to PyPI, and generate release notes. So the packages were published, but no GitHub release or notes were posted.
Fix
Change
contents: readtocontents: writefor the release job, which is the permission needed to create a release.id-token: write, used for PyPI trusted publishing, is unchanged.The release can only be fully checked by the next tag push.
🤖 Generated with Claude Code