Update to use @actions/cache 4.0.3 package & prepare for new release #1577
+356
−20
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.
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: