Skip to content

ci: declare workflow-level contents: read on 7 CI workflows#2672

Open
arpitjain099 wants to merge 1 commit into
eclipse-platform:masterfrom
arpitjain099:chore/declare-workflow-perms
Open

ci: declare workflow-level contents: read on 7 CI workflows#2672
arpitjain099 wants to merge 1 commit into
eclipse-platform:masterfrom
arpitjain099:chore/declare-workflow-perms

Conversation

@arpitjain099
Copy link
Copy Markdown

Adds workflow-level permissions: contents: read to seven CI workflows that run pure checks or validation:

  • checkDependencies, ci, codeql, doCleanCode, pr-checks, unit-tests, version-increments

The cap is at the workflow level only. Jobs that genuinely need a wider scope (e.g., the codeql analyze job typically needs security-events: write) can still declare it at the job level.

Same post-CVE-2025-30066 (tj-actions/changed-files compromise) hardening pattern. YAML validated locally with yaml.safe_load on each touched file.

All 7 workflows (checkDependencies, ci, codeql, doCleanCode, pr-checks, unit-tests, version-increments) just run checks and validation. No GitHub API writes from the workflows themselves at the workflow level.

For workflows where individual jobs need a higher scope (e.g., codeql analyze typically needs security-events: write), job-level permissions can still override upward. This PR only adds the workflow-level cap.

Same post-CVE-2025-30066 (tj-actions/changed-files) hardening pattern. yaml.safe_load validated on each touched file.

Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
@arpitjain099 arpitjain099 force-pushed the chore/declare-workflow-perms branch from d2e6468 to 59e3c2c Compare May 26, 2026 06:31
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