Repository navigation
ci(integration): cap GITHUB_TOKEN to contents: read - #3761
Merged
atakavci merged 2 commits intoMay 25, 2026
Merged
Conversation
integration workflow runs the integration test suite; no GitHub API writes from the workflow. contents: read at workflow level is appropriate. Post-CVE-2025-30066 hardening shape. yaml.safe_load validated. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
Collaborator
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.
The
integrationworkflow runs the integration test suite. No GitHub API writes from the workflow, so a workflow-levelcontents: readis the right cap for the defaultGITHUB_TOKEN.Same post-CVE-2025-30066 (
tj-actions/changed-files) hardening pattern. YAML validated locally.Note
Low Risk
Single CI permissions block with no application or runtime behavior changes.
Overview
The integration workflow now declares workflow-level
permissionswithcontents: read, capping the defaultGITHUB_TOKENinstead of inheriting broader repo defaults.This matches the same least-privilege hardening used elsewhere after
tj-actions/changed-files-related supply-chain concerns; the job only needs to read the repo to run tests, not write via the token.Reviewed by Cursor Bugbot for commit 7f96ee0. Bugbot is set up for automated code reviews on this repo. Configure here.