chore: pin GitHub Actions to specific commit hashes #41
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.
Motivation / Background
This Pull Request has been created to improve the security and stability of our GitHub Actions workflow by pinning action versions to specific commit hashes. This follows the security best practice recommended by GitHub to prevent potential supply chain attacks.
Detail
This Pull Request changes the version references in our GitHub Actions workflow from floating version tags to specific commit hashes:
actions/checkout
fromv4
tov4.2.2
(commit hash:11bd71901bbe5b1630ceea73d27597364c9af683
)actions/setup-java
fromv3
tov3.13.0
(commit hash:0ab4596768b603586c0de567f2430c30f5b0d2b0
)actions/cache
fromv2
to commit hash8492260343ad570701412c2f464a5877dc76bace
of the same versionruby/setup-ruby
fromv1
tov1.227.0
(commit hash:1a615958ad9d422dd932dc1d5823942ee002799f
)Benefits of this change:
Checklist