ci: Add explicit permissions for release-please#61
Merged
aaron-zeisler merged 1 commit intoJul 22, 2026
Conversation
Without an explicit permissions block, the job's GITHUB_TOKEN is read-only under the tightened default, so release-please-action fails with 403 Resource not accessible by integration when creating the release branch and PR. Mirrors the create-prs job in check-go-versions.yml.
aaron-zeisler
changed the title
aaron-zeisler
marked this pull request as ready for review
July 22, 2026 16:44
joker23
approved these changes
Jul 22, 2026
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
2 participants
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.
Summary
permissions: { contents: write, pull-requests: write }block to.github/workflows/release-please.yml, mirroring thecreate-prsjob in.github/workflows/check-go-versions.yml.Background
The Run Release Please workflow started failing with a 403 after merging #60:
The job had no
permissions:block, so itsGITHUB_TOKENwas read-only under the (now-tightened) default, andrelease-please-actioncouldn't create the release branch or PR. This blocked cutting v1.11.1, which contains the stream-close deadlock fix from #60.