Add explicit GITHUB_TOKEN permissions to workflow files#629
Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
The publish workflow does git commit, tag, and push, which requires contents: write. Caught by Cursor Bugbot review.
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
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: read }to 7 workflow files missing explicit permission scopingFiles changed
testing-dependency-rest.yamltesting-dependency-grpc.yamltesting-dependency-asyncio.yamltesting-dependency.yamlcleanup-nightly.yamlbuild-and-publish-docs.yamlpublish-to-pypi.yamlTest plan
Note
Low Risk
Low risk workflow-only change that tightens default
GITHUB_TOKENaccess; main risk is an unexpected permissions mismatch causing workflow failures (notably PyPI publishing/tag pushes).Overview
Adds explicit
permissionsblocks to several GitHub Actions workflows to follow least-privilege defaults.Most workflows are scoped to
contents: read, while the PyPI release workflow is explicitly grantedcontents: writeto support tagging/pushing during releases.Written by Cursor Bugbot for commit 49b5bf2. This will update automatically on new commits. Configure here.