ci: pin GitHub Actions to commit SHAs#81
Merged
Conversation
Pin all mutable-tag third-party actions in ci.yml and release.yml to their resolved commit SHAs with trailing version comments, closing the supply-chain gap where a compromised or re-tagged upstream release could silently run in CI.
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 free
to 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.
Pins every mutable-tag third-party action in ci.yml and release.yml to a full commit SHA with a version comment, per the #66 PR 6 security review follow-up. Same jobs, same versions — each SHA is the exact commit its tag pointed to at pin time, independently verified twice via the GitHub refs API (annotated tags dereferenced to commit objects).
Left as-is:
google/osv-scanner-action(already SHA-pinned) and thedocker://ghcr.io/gitleaks/gitleaks:v8.30.1image reference (digest-pinning is a registry mechanism, tracked as a possible follow-up).Known tradeoff:
dtolnay/rust-toolchain@stableandtaiki-e/install-action@cargo-llvm-covare inherently mutable refs, now frozen at their 2026-07 heads — they need manual bumps to pick up new upstream releases.Closes #77.
🤖 Generated with Claude Code