chore: pin GitHub actions versions to hashes#10169
Merged
Merged
Conversation
Jefffrey
commented
Jun 21, 2026
| steps: | ||
| - name: Cache Cargo | ||
| uses: actions/cache@v4 | ||
| uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5 |
Contributor
Author
There was a problem hiding this comment.
this is the only upgrade; not sure why this was stuck on v4 (why dependabot didnt bump it for us 🤔)
all other changes are just pinning to same hash as their version
alamb
approved these changes
Jun 22, 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.
Which issue does this PR close?
Rationale for this change
Similar to what we did in DataFusion, pin to hash since tags can be changed and potentially be susceptible to supply chain attacks
What changes are included in this PR?
Pin all versions to their hashes
Are these changes tested?
Are there any user-facing changes?