Uh oh!
There was an error while loading. Please reload this page.
chore: pin GitHub Actions to commit SHAs - #103
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 CI pinning with no application or security-logic changes; behavior should match the previously referenced action versions.
Overview
Pins remaining mutable GitHub Action refs to full commit SHAs while keeping the original version in
#comments, aligning release and security scanner composites with org supply-chain hardening.In
publish-release,MetaMask/github-toolsget-tokenandupdate-major-version-tagmove from@v1to SHA8a343dd29c95b8478e0e92d8eed915ad50dcfaf0(v1.18.0). Incodeql-actionandsemgrep-action,github/codeql-actionsteps already used that SHA; comments are clarified from# v4to# v4.36.2for init, analyze, and upload-sarif.No step inputs, env, or scanner behavior change—only which immutable action revision runs.
Reviewed by Cursor Bugbot for commit 19a97bd. Bugbot is set up for automated code reviews on this repo. Configure here.