Update to use @actions/cache 4.0.3 package & prepare for new release by @salmanmkc in #1577 (SAS tokens for cache entries are now masked in debug logs)
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).
If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0
If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
[!WARNING]
This version was incorrectly released using a SHA pointing to a newer version for immutable actions only. Please use v3.4.2 (or v3) instead.
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).
If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0
If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Fix zstd not working for windows on gnu tar in issues.
Allow users to provide a custom timeout as input for aborting cache segment download using the environment variable SEGMENT_DOWNLOAD_TIMEOUT_MIN. Default is 60 minutes.
Fix for the download stuck problem has been added in actions/cache for users who were intermittently facing the issue. As part of this fix, new timeout has been introduced in the download step to stop the download if it doesn't complete within an hour and run the rest of the workflow without erroring out.
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
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.
This PR contains the following updates:
Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.
Release Notes
actions/cache (actions/cache)v6.1.0
Compare Source
What's Changed
Full Changelog: actions/cache@v6...v6.1.0
v6.0.0
Compare Source
What's Changed
Full Changelog: actions/cache@v5...v6.0.0
v6
Compare Source
v5.1.0
Compare Source
What's Changed
Full Changelog: actions/cache@v5...v5.1.0
v5.0.5
Compare Source
What's Changed
Full Changelog: actions/cache@v5...v5.0.5
v5.0.4
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v5...v5.0.4
v5.0.3
Compare Source
What's Changed
Full Changelog: actions/cache@v5...v5.0.3
v5.0.2: v.5.0.2
Compare Source
v5.0.2
What's Changed
When creating cache entries, 429s returned from the cache service will not be retried.
v5.0.1
Compare Source
v5.0.1
What's Changed
v5.0.0
What's Changed
Full Changelog: actions/cache@v5...v5.0.1
v5.0.0
Compare Source
What's Changed
Full Changelog: actions/cache@v4.3.0...v5.0.0
v5
Compare Source
v4.3.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4...v4.3.0
v4.2.4
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4...v4.2.4
v4.2.3
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4.2.2...v4.2.3
v4.2.2
Compare Source
What's Changed
Full Changelog: actions/cache@v4.2.1...v4.2.2
v4.2.1
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4.2.0...v4.2.1
v4.2.0
Compare Source
⚠️ Important Changes
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).
If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0
If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
Full Changelog: actions/cache@v4.1.2...v4.2.0
v4.1.2
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4.1.1...v4.1.2
v4.1.1
Compare Source
What's Changed
Full Changelog: actions/cache@v4.1.0...v4.1.1
v4.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4.0.2...v4.1.0
v4.0.2
Compare Source
What's Changed
Full Changelog: actions/cache@v4.0.1...v4.0.2
v4.0.1
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4...v4.0.1
v4.0.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v4.0.0
v4
Compare Source
v3.5.0
Compare Source
Full Changelog: actions/cache@v3...v3.5.0
v3.4.3
Compare Source
What's Changed
Full Changelog: actions/cache@v3.4.2...v3.4.3
v3.4.2
Compare Source
What's Changed
Full Changelog: actions/cache@v3.4.0...v3.4.2
v3.4.1
Compare Source
v3.4.0
Compare Source
⚠️ Important Changes
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).
If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0
If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
Full Changelog: actions/cache@v3.3.3...v3.4.0
v3.3.3
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.3
v3.3.2
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.2
v3.3.1
Compare Source
What's Changed
Full Changelog: actions/cache@v3...v3.3.1
v3.3.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.0
v3.2.6
Compare Source
What's Changed
Full Changelog: actions/cache@v3...v3.2.6
v3.2.5
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.5
v3.2.4
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.4
v3.2.3
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.3
v3.2.2
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3.2.1...v3.2.2
v3.2.1
Compare Source
What's Changed
Full Changelog: actions/cache@v3.2.0...v3.2.1
v3.2.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.0
v3.0.11
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.0.11
v3.0.10
Compare Source
v3.0.9
Compare Source
v3.0.8
Compare Source
What's Changed
v3.0.7
Compare Source
What's Changed
v3.0.6
Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.0.6
v3.0.5
Compare Source
Removed error handling by consuming actions/cache 3.0 toolkit, Now cache server error handling will be done by toolkit.
v3.0.4
Compare Source
In this release, we have fixed the tar creation error while trying to create it with path as ~/ home folder on ubuntu-latest.
v3.0.3
Compare Source
Fixed avoiding empty cache save when no files are available for caching. (#624)
v3.0.2
Compare Source
This release adds the support for dynamic cache size cap on GHES.
v3.0.1
Compare Source
Configuration
📅 Schedule: (in timezone America/Los_Angeles)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.