Skip to content

ci: declare workflow-level contents: read on backend-test and regression#713

Open
arpitjain099 wants to merge 1 commit into
pingcap:mainfrom
arpitjain099:chore/declare-workflow-perms
Open

ci: declare workflow-level contents: read on backend-test and regression#713
arpitjain099 wants to merge 1 commit into
pingcap:mainfrom
arpitjain099:chore/declare-workflow-perms

Conversation

@arpitjain099
Copy link
Copy Markdown

Pins the default GITHUB_TOKEN to contents: read on:

  • backend-test.yml (PR-gated pytest run scoped to backend/** changes)
  • regression.yml (manual workflow_dispatch regression suite)

Neither calls the GitHub API beyond checkout. verify.yml is intentionally untouched (uses cache: pnpm, would need actions: write for the cache-save path and that scope decision belongs to maintainers).

Same hardening shape that became standard after CVE-2025-30066 (tj-actions/changed-files exfiltrated GITHUB_TOKEN from caller workflow logs in March).

YAML validated locally with yaml.safe_load.

Both workflows only run tests via checkout + Python/dataset operations; neither calls the GitHub API beyond fetching the repo. Workflow-level contents: read is the right ceiling for the default GITHUB_TOKEN.

verify.yml is intentionally left out (uses cache: pnpm, would need actions: write for cache save).

Same post-CVE-2025-30066 hardening shape (tj-actions/changed-files compromise). yaml.safe_load validated.

Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 21, 2026

@arpitjain099 is attempting to deploy a commit to the pingcap Team on Vercel.

A member of the Team first needs to authorize it.

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.

1 participant