Skip to content

Conversation

@picatz
Copy link
Contributor

@picatz picatz commented Oct 29, 2025

Summary

  • .github/workflows/ci.yml: Added workflow-level permissions block granting contents: read at .github/workflows/ci.yml:8 so setup-protoc and reusable workflow calls run with least-privilege GITHUB_TOKEN; workflow-only edit, no tests executed.
  • .github/workflows/package.yml: Added contents: read permissions at .github/workflows/package.yml:8 to cover checkout, artifact, and setup-protoc steps without excess token scope; workflow metadata change only, no tests run.
  • .github/workflows/run-bench.yml: Declared workflow permissions contents: read at .github/workflows/run-bench.yml:5 to limit GITHUB_TOKEN exposure for checkout and setup-protoc when invoked via workflow_call; appended trailing newline.
  • .github/workflows/nightly.yml: Set permissions: contents: read at .github/workflows/nightly.yml:7 so nightly dispatcher inherits restricted token scope when invoking run-bench; no runtime changes to jobs.
  • .github/workflows/omes.yml: Introduced workflow-level contents: read permissions at .github/workflows/omes.yml:7 to restrict token used when calling external reusable workflow; no tests required for YAML edit.

This change was made by an automated process to ensure all GitHub Actions workflows have explicitly defined permissions as per best practices.
@picatz picatz requested a review from a team as a code owner October 29, 2025 16:09
@cretz cretz merged commit a0bb2c9 into main Oct 29, 2025
15 of 18 checks passed
@cretz cretz deleted the security-campaign/set-explicit-github-actions-permissions branch October 29, 2025 18:55
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