ci: pin GitHub Actions to commit SHAs (supply-chain hardening)#132
Merged
Conversation
Every `uses:` is pinned to a full 40-char commit SHA with a trailing `# vX.Y.Z` comment, replacing floating major tags (and the `release/v1` branch for gh-action-pypi-publish). A mutable ref can be silently repointed if an action repo or maintainer account is compromised (cf. tj-actions/changed-files, March 2025); a SHA pin cannot. Pins target the latest release of each action, all reviewed this session. Dependabot (github-actions ecosystem, already configured) updates SHA pins and bumps the version comment alongside, so security fixes still arrive as reviewable PRs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Supply-chain hardening, fan-out from the wlsqm pilot.
Pins every
uses:to an immutable commit SHA (+# vX.Y.Zcomment) instead of a floating tag/branch. A floating ref can be silently repointed if an action repo or maintainer account is compromised (cf.tj-actions/changed-files, March 2025); a SHA cannot. SHAs target the latest release of each action — all reviewed this session (codecov v7.0.0 GPG-signed with maintainer-key continuity; cibuildwheel v4.0.0 PyPA/henryiii). Dependabot understands SHA-pinned actions and bumps both the SHA and the comment, so updates still flow as reviewable PRs.Pure hardening — pinned commits are the current latest releases, so CI runs the same code.
🤖 Generated with Claude Code