ci: grant issues and pull-requests write to release workflow#598
Merged
Conversation
auto shipit posts a released comment on linked issues after publishing; the GITHUB_TOKEN needs issues:write and pull-requests:write for that. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
commit: |
yoannfleurydev
added
patch
|
🚀 PR was released in |
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.
Summary
issues: writeandpull-requests: writeto the Node CI workflow permissions soauto shipitcan post its "released" comment on linked issues/PRs (fixes the403 Resource not accessible by integrationseen on the v12.0.0 release)..context/directory used by the Conductor workspace.Test plan
🤖 Generated with Claude Code