chore: pin GitHub Actions to commit SHAs - #282
Conversation
Pin every `uses:` ref in .github/workflows and composite actions to a
full 40-character commit SHA, with the original tag preserved as a
comment, e.g.
uses: actions/checkout@11bd719 # v4
Tags and branches are mutable; commit SHAs are not. Pinning to a SHA
closes a supply-chain vector where a compromised action could replace
what runs in CI without changing the tag we reference.
Generated mechanically with `pinact run`
(https://github.com/suzuki-shunsuke/pinact). No version bumps were
applied (strict pin).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit c596e96. Configure here.
| contents: read | ||
| steps: | ||
| - uses: actions/checkout@v3 | ||
| - uses: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744 # v3.6.0 |
There was a problem hiding this comment.
Mutable @main refs left unpinned across all workflows
High Severity
This PR claims to "pin every uses: ref" and bring the repo into TechOps compliance, but all four workflow files still reference ConsenSys/docs-gha/*@main — a mutable branch ref that is the same class of supply-chain risk this PR exists to close. Per the PR description, workflows referencing mutable tags or branches will be blocked from running after June 8, 2026, so these workflows will break at that deadline.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit c596e96. Configure here.
1 participant
Summary
Pin every
uses:ref in.github/workflows/(and any composite actionfiles) to a full 40-character commit SHA, with the original tag
preserved as a
# vXcomment.Why
Tags and branches are mutable, so a compromised action can replace what
runs in our pipelines without changing the tag we reference. Pinning to
a SHA closes that supply-chain vector. See GitHub's hardening guide:
https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions.
Deadline
TechOps is enforcing SHA-pinned GitHub Actions across the org by
June 8, 2026. Merging this PR brings the repo into compliance ahead
of the cut-over; after that date workflows that still reference
mutable tags or branches will be blocked from running.
How
Generated mechanically with
pinact run.No version bumps were applied (strict pin); follow-up upgrades can come
from Renovate or a separate
pinact run -uPR.Test plan
Note
Low Risk
Low risk mechanical CI change that only pins
actions/checkoutto a specific commit for supply-chain hardening; workflow behavior should remain effectively the same aside from using an exact action revision.Overview
Pins
actions/checkoutfrom the mutable@v3tag to a specific commit SHA (# v3.6.0) across thebuild,lint,links, andcaseGitHub Actions workflows to improve supply-chain security and reproducibility.Reviewed by Cursor Bugbot for commit c596e96. Bugbot is set up for automated code reviews on this repo. Configure here.