Uh oh!
There was an error while loading. Please reload this page.
chore: pin GitHub Actions to commit SHAs - #97
Open
BGos87 wants to merge 1 commit into
Open
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).
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 freeto 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
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.
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 -uPR.Test plan
Note
Low Risk
Mechanical ref pinning with no version bumps or application code changes; CI behavior should match the previously referenced tags.
Overview
Pins every third-party and MetaMask
uses:reference under.github/workflows/from floating tags (e.g.@v1,@v4) to 40-character commit SHAs, with the original version noted in a# vXcomment. No workflow logic, inputs, or job structure changes—only how actions are resolved at runtime.Coverage spans build/lint/test, main (including release detection), create-release-pr, publish-release (GitHub release, artifact upload/download, npm dry-run/publish, checkout), publish-docs, and security-code-scanner. Actions touched include
MetaMask/action-checkout-and-setup,action-create-release-pr,action-is-release,action-publish-release,action-npm-publish,action-security-code-scanner, plusactions/upload-artifact,actions/download-artifact, andactions/checkout.Reviewed by Cursor Bugbot for commit e09c43a. Bugbot is set up for automated code reviews on this repo. Configure here.