Skip to content

ci(integration): cap GITHUB_TOKEN to contents: read - #3761

Merged
atakavci merged 2 commits into
redis:mainfrom
arpitjain099:chore/declare-workflow-perms-int
May 25, 2026
Merged

atakavci merged 2 commits into
redis:mainfrom
arpitjain099:chore/declare-workflow-perms-int

Conversation

@arpitjain099

@arpitjain099 arpitjain099 commented May 24, 2026 •

Copy link
Copy Markdown
Contributor

The integration workflow runs the integration test suite. No GitHub API writes from the workflow, so a workflow-level contents: read is the right cap for the default GITHUB_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 permissions with contents: read, capping the default GITHUB_TOKEN instead 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.

arpitjain099 and others added 2 commits May 24, 2026 11:35
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>
@atakavci
atakavci merged commit 2a49a07 into redis:main May 25, 2026
13 checks passed
@a-TODO-rov

Copy link
Copy Markdown
Collaborator

Hey, @atakavci . Could you check also #3748

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

⌂ 换网址