fix(ci): add issues:write permission for semantic-release#96
Merged
pablofmena merged 1 commit intomasterfrom Apr 6, 2026
Merged
fix(ci): add issues:write permission for semantic-release#96pablofmena merged 1 commit intomasterfrom
pablofmena merged 1 commit intomasterfrom
Conversation
The @semantic-release/github plugin needs issues:write to create failure-reporting issues. Without it, the release job fails with 403 "Resource not accessible by integration". Made-with: Cursor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
This was referenced Apr 6, 2026
Collaborator
|
🎉 This PR is included in version 5.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Scope
Follow-up to #89 (switch from
CI_TOKENPAT toGITHUB_TOKEN). The release workflow was failing because:@semantic-release/githubneedsissues: writeto create failure-reporting issues — the workflow only grantedcontents: writeandid-token: write.masterrestricted pushes tointervene-ciuser and two teams —github-actions[bot]was not allowed. This was fixed separately by adding the GitHub Actions app to the push restrictions via the API.Implementation
Adds
issues: writeto the workflow-levelpermissionsblock inrelease.yml.The branch protection change (adding
github-actionsto the allowed push actors) was applied directly via the GitHub API and is already in effect.How To Test
Merge this PR and wait for the next releasable commit to land on
master. The release workflow should complete without the403 Resource not accessible by integrationerror or theEGITNOPERMISSIONpush failure.Made with Cursor