Skip to content

chore: pin GitHub Actions to commit SHAs - #184

Open
BGos87 wants to merge 1 commit into
mainfrom
chore/pin-github-actions-20260923
Open

BGos87 wants to merge 1 commit into
mainfrom
chore/pin-github-actions-20260923

Conversation

@BGos87

@BGos87 BGos87 commented Sep 23, 2026 •

Copy link
Copy Markdown

Summary

Pin every uses: ref in .github/workflows/ (and any composite action
files) to a full 40-character commit SHA, with the original tag
preserved as a # vX comment.

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.
Merging this PR brings the repo into compliance; workflows that still
reference mutable tags or branches may 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 -u PR.

Test plan

  • CI green on this branch

Note

Low Risk
Workflow-only pinning with no application or runtime changes; release/npm steps use the same action versions, just immutably referenced.

Overview
Replaces mutable @v* (and similar) refs on third-party and MetaMask workflow actions with immutable 40-character commit SHAs, keeping the original tag in a # vX comment for readability.

Coverage spans the main CI and release pipelines—build/lint/test, main orchestration, create release PR, publish release (including npm dry-run/publish and cache restore), and GitHub Pages dapp publish. Typical pins include actions/checkout, actions/setup-node, actions/cache, and MetaMask release/publish actions; workflow logic and job matrices are unchanged.

This is a supply-chain hardening change for org compliance; behavior should match the previously referenced tag versions until a deliberate SHA bump.

Reviewed by Cursor Bugbot for commit eaae17b. Bugbot is set up for automated code reviews on this repo. Configure here.

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).
yarn install
yarn build
- uses: actions/cache@v3
- uses: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c # v3.5.0
with:
ref: ${{ github.sha }}
- uses: actions/cache@v3
- uses: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c # v3.5.0
with:
ref: ${{ github.sha }}
- uses: actions/cache@v3
- uses: actions/cache@6f8efc29b200d32929f49075959781ed54ec270c # v3.5.0

This branch has not been deployed

No deployments
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.

2 participants