-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Update to use @actions/cache 4.0.3 package & prepare for new release #1577
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
Conversation
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.
steps:%0A%20%20-%20uses%3A%20actions/checkout@v4%0A%0A%20%20-%20uses:%20actions/cache/restore@v4%0A%20%20%20%20id:%20cache%0A%20%20%20%20with:%0A%20%20%20%20%20%20path:%20path/to/dependencies%0A%20%20%20%20%20%20key:%20$%7B%7B%20runner.os%20%7D%7D-$%7B%7B%20hashFiles('**/lockfiles')%20%7D%7D%0A%20%20%20%20%20%20fail-on-cache-miss:%20true%0A%0A%20%20-%20name:%20Build%0A%20%20%20%20run:%20/build.sh
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.
approved
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.
Nice
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.
Nice
Description
This pull request includes updates to the version of the
@actions/cache
dependency in both the.licenses/npm/@actions/cache.dep.yml
file and thepackage.json
file.Dependency version updates:
.licenses/npm/@actions/cache.dep.yml
: Updated@actions/cache
version from4.0.2
to4.0.3
.package.json
: Updated@actions/cache
version from4.0.2
to4.0.3
.Package version update:
package.json
: Updated package version from4.2.2
to4.2.3
.Updates to the
@actions/cache
dependency4.0.3
Motivation and Context
SAS tokens are sensitive information and should not be exposed in logs. This change masks the SAS token in the logs. The cache version is also logged to help with debugging.
How Has This Been Tested?
Done testing on a workflow that uses the cache save/restore and when there is a cache miss, I verified that it also prints out the version of cache that was requested.
Screenshots (if appropriate):
Types of changes
Checklist: