fix: add missing permissions to release-comment workflow #1757
+2
−0
Conversation
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
The github-release-commenter action requires `issues: write` permission to comment on issues that are referenced by PRs (e.g., "Fixes #1754"). Without this permission, the action fails with "Resource not accessible by integration". Also adds `contents: read` to ensure the action can read release/commit information.
maxisbey
added
bug
Contributor
Author
|
Superseded by #1758 which removes the workflow entirely. |
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.
Fixes the failing
Comment on Released PRsworkflow by adding missing GitHub token permissions.Motivation and Context
The workflow at https://github.com/modelcontextprotocol/python-sdk/actions/runs/20068484009 failed with:
This happened because the
github-release-commenteraction tried to comment on issue #1754 (referenced via "Fixes #1754" in PR #1755), but the workflow only hadpull-requests: writepermission.How Has This Been Tested?
This is a workflow permissions fix. The next release will verify the fix works correctly.
Breaking Changes
None.
Types of changes
Checklist
Additional context
Added permissions:
issues: write- Required to comment on issues referenced by PRscontents: read- Required to read release/commit informationAI Disclaimer