Skip to content

chore: pin GitHub Actions to commit SHAs - #118

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

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

Conversation

@BGos87

@BGos87 BGos87 commented Sep 21, 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 change with no application code or runtime behavior impact; pins existing action versions to fixed commits.

Overview
This PR hardens CI supply chain by replacing mutable action tags in build-lint.yml with immutable 40-character commit SHAs, keeping the original version in # vX comments for readability.

actions/checkout, actions/setup-node, and actions/cache are pinned to the same releases that were previously referenced (v2.8.0, v2.5.2, and v2 respectively). Build, lint, cache, and matrix steps are unchanged—only what GitHub resolves for each uses: line changes.

Reviewed by Cursor Bugbot for commit 954454e. 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).
@BGos87
BGos87 requested a review from a team as a code owner September 21, 2026 19:01
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.

1 participant