ci: harden workflows — permissions, concurrency, SHA-pinned actions#39
Merged
Conversation
…loses #25) Apply standard supply-chain and efficiency hardening to all three workflows: - Add `permissions: { contents: read }` (least privilege; none of the jobs need write access). - Add a `concurrency` group keyed on workflow + ref with cancel-in-progress, so superseded runs (e.g. rapid pushes to a PR) are cancelled. - Pin actions to full commit SHAs with version comments: - actions/checkout @34e1148 # v4.3.1 - actions/setup-node @49933ea # v4.4.0 - pnpm/action-setup @fc06bc1 # v4.4.0 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Closes #25.
Standard supply-chain + efficiency hardening across all three workflows:
permissions: { contents: read }— least privilege; none of the jobs need write access.concurrencygroup keyed on workflow + ref withcancel-in-progress: true— superseded runs (rapid PR pushes) get cancelled instead of piling up.actions/checkout@34e1148# v4.3.1actions/setup-node@49933ea# v4.4.0pnpm/action-setup@fc06bc1# v4.4.0Verification
templates.test.ts(which reads the workflow files) still passes; the workflow YAML is validated by this PR's own CI run.🤖 Generated with Claude Code