ci: add least-privilege permissions to workflows#47
Merged
Conversation
Add explicit top-level permissions blocks to all GitHub Actions workflows, which previously inherited the repository default token scope. Write operations in these workflows use PROSOPONATOR_PAT, so the built-in GITHUB_TOKEN only needs contents: read (plus actions: write in cache.yml for cache management).
✅ Deploy Preview for peaceful-pothos-9e62ce ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
All GitHub Actions workflows in this repo previously had no
permissions:block, so each inherited the repository defaultGITHUB_TOKENscope (potentially read/write-all).This adds explicit least-privilege top-level permissions to all 6 workflows.
Details
Write operations (releases, PR creation,
git push) in these workflows authenticate viaPROSOPONATOR_PAT, not the built-inGITHUB_TOKEN. So the default token only needs:contents: read— all workflows (for checkout)actions: write—cache.ymladditionally, for cache save/cleanupNo write scope is required on the built-in token because the PAT carries auth for all push/release/PR steps.