chore: pin GitHub Actions by SHA#265
Merged
Merged
Conversation
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.
Summary
GitHub recommends pinning third-party workflow actions to full commit SHAs so workflow execution cannot silently change when a mutable tag is moved. This PR updates every referenced GitHub Action in this repository to the latest published release SHA and keeps the release tags in inline comments for maintainability.
Context
This updates all action references under
.github/workflows/to immutable SHAs foractions/checkout,pnpm/action-setup,actions/setup-node, andactions/stale.It also removes
setup-nodepackage-manager caching from the release workflow so release runs stay deterministic and do not rely on restored cache state.Proposed Testing Scenario
Review the workflow diffs and confirm each
uses:entry points to a full commit SHA with the corresponding release tag preserved in the trailing comment.Trigger the
Releaseworkflow throughworkflow_dispatchand confirm the Node setup step runs without cache restoration while the rest of the release job still completes normally.