Pin GitHub Actions to commit SHAs#28
Merged
Merged
Conversation
HungKNguyen
approved these changes
Jun 9, 2026
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
2 participants
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.
What changed
Pinned the external GitHub Actions used by
.github/workflows/tests.ymlto verified full-length commit SHAs while preserving# v4comments for human-readable release context.Why
Mutable action refs such as
@v4can move without any repository change. Pinning to commit SHAs reduces the supply-chain risk from moved tags or compromised upstream action repositories.Validation
Verified each upstream
v4tag withgit ls-remote --tagsagainst the official action repositories.pnpm/action-setup@v4is an annotated tag, so the workflow pins the peeled commit fromrefs/tags/v4^{}. Also checked that no remaining workflowuses:refs point at mutable refs and rangit diff --check.pnpm exec actionlintcould not run locally because the repository does not configure a pnpm version for the active local tool manager.