Skip to content

ci: pin GITHUB_TOKEN to contents: read - #118

Open
arpitjain099 wants to merge 1 commit into
trinodb:masterfrom
arpitjain099:chore/workflow-perms
Open

ci: pin GITHUB_TOKEN to contents: read#118
arpitjain099 wants to merge 1 commit into
trinodb:masterfrom
arpitjain099:chore/workflow-perms

Conversation

@arpitjain099

Copy link
Copy Markdown
Member

The ci workflow runs the Maven build + integration tests. No GitHub API writes happen from the workflow, so the default GITHUB_TOKEN can be capped at contents: read at the workflow level.

Same supply-chain hardening pattern the wider GitHub Actions community adopted after CVE-2025-30066 (tj-actions/changed-files exfiltrated unspoken token scopes from caller workflow logs).

YAML validated locally.

The CI workflow runs Maven build + integration tests. No GitHub API writes from the workflow, so the default GITHUB_TOKEN can be capped at contents: read.

Same per-workflow least-privilege practice that came out of CVE-2025-30066 (the tj-actions/changed-files compromise leaked unspoken token scopes from caller workflow logs).

Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
@cla-bot

cla-bot Bot commented May 18, 2026

Copy link
Copy Markdown

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@arpitjain099

Copy link
Copy Markdown
Member Author

CLA emailed

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant