ci: fixing release please permissions#352
Merged
tanderson-ld merged 1 commit intomainfrom Apr 29, 2026
Merged
Conversation
keelerm84
approved these changes
Apr 28, 2026
Contributor
|
Is this change necessary in all of our repositories? |
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
3 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.
Note
Low Risk
Low risk: only adjusts GitHub Actions workflow permissions for the
call-workflow-publishjob, affecting CI/release automation but not application runtime code.Overview
Ensures the
call-workflow-publishjob inrelease-please.ymlexplicitly requestsid-token: writeandcontents: writepermissions when invoking the reusablepublish.ymlworkflow, so the publish step has the access it needs after a release is created.Reviewed by Cursor Bugbot for commit 11779f1. Bugbot is set up for automated code reviews on this repo. Configure here.