-
Notifications
You must be signed in to change notification settings - Fork 64
build: update all github actions #3561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,7 +13,7 @@ runs: | |
| using: composite | ||
| steps: | ||
| - name: Configure action caching for bazel version downloaded by bazelisk | ||
| uses: actions/cache@cdf6c1fa76f9f475f3d7449005a359c84ca0f306 # v5.0.3 | ||
| uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4 | ||
| with: | ||
| path: | | ||
| ~/.cache/bazelisk | ||
|
|
@@ -27,7 +27,7 @@ runs: | |
| shell: bash | ||
|
|
||
| - name: Configure action caching for bazel repository cache | ||
| uses: actions/cache@cdf6c1fa76f9f475f3d7449005a359c84ca0f306 # v5.0.3 | ||
| uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For improved readability and maintainability, consider using the version tag directly instead of the commit SHA. While pinning to a SHA is a secure practice, using a specific version tag like uses: actions/cache@v5.0.4 |
||
| with: | ||
| # Note: Bazel repository cache is located in system locations and cannot use | ||
| # a shared cache between different runner operating systems. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For improved readability and maintainability, consider using the version tag directly instead of the commit SHA. While pinning to a SHA is a secure practice, using a specific version tag like
v5.0.4is also secure against accidental updates and makes the workflow easier to understand at a glance.