Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 17, 2024

This PR contains the following updates:

Package Type Update Change
actions/cache action major v2.1.6 -> v4.3.0

Release Notes

actions/cache (actions/cache)

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

[!IMPORTANT]
As a reminder, there were important backend changes to release v4.2.0, see those release notes and the announcement for more details.

Full Changelog: actions/cache@v4.2.1...v4.2.2

v4.2.1

Compare Source

What's Changed

[!IMPORTANT]
As a reminder, there were important backend changes to release v4.2.0, see those release notes and the announcement for more details.

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

v3.5.0

Compare Source

  • Bump actions/cache to v4.1.0

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

[!IMPORTANT]
As a reminder, there were important backend changes to release v3.4.0, see those release notes and the announcement for more details.

Full Changelog: actions/cache@v3.4.0...v3.4.2

v3.4.1

Compare Source

[!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.

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

  • Fix a bug with sorting inputs.
  • Update definition for restore-keys in README.md

v3.0.9

Compare Source

  • Enhanced the warning message for cache unavailability in case of GHES.

v3.0.8

Compare Source

What's Changed

  • 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.

v3.0.7

Compare Source

What's Changed
  • 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.

v3.0.6

Compare Source

What's Changed
  • Add example for clojure lein project dependencies by @​shivamarora1 in PR #​835
  • Update toolkit's cache npm module to latest. Bump cache version to v3.0.6 by @​pdotl in PR #​887
  • Fix issue #​809 where cache save/restore was failing for Amazon Linux 2 runners due to older tar version
  • Fix issue #​833 where cache save was not working for caching github workspace directory
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

  • Added support for caching from GHES 3.5.
  • Fixed download issue for files > 2GB during restore.

v3.0.0

Compare Source

  • This change adds a minimum runner version(node12 -> node16), which can break users using an out-of-date/fork of the runner. This would be most commonly affecting users on GHES 3.3 or before, as those runners do not support node16 actions and they can use actions from github.com via github connect or manually copying the repo to their GHES instance.

  • Few dependencies and cache action usage examples have also been updated.

v2.1.8: Updating actions/core to version 1.10.0

Compare Source

The ::save-state and ::set-output are deprecated. The newer version of actions/core >1.10.0 uses the new syntax for save and set output. After this change, customers using actions/cache@​v2 won't see deprecation warning message.

v2.1.7

Compare Source

Support 10GB cache upload using the latest version 1.0.8 of @actions/cache


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from d95f9f0 to f1fafee Compare February 29, 2024 18:57
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from f1fafee to e6ccb9b Compare March 19, 2024 18:20
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch 3 times, most recently from 532504c to b37beb2 Compare October 4, 2024 21:41
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from b37beb2 to 1496558 Compare October 8, 2024 19:58
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from 1496558 to 5b33620 Compare October 22, 2024 14:01
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from 5b33620 to 7299abc Compare December 5, 2024 19:26
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from 7299abc to f85e847 Compare February 18, 2025 21:04
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from f85e847 to 3a67813 Compare February 27, 2025 17:01
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from 3a67813 to 611fadb Compare March 19, 2025 20:26
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from 611fadb to 988185d Compare August 7, 2025 15:06
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from 988185d to a9819da Compare September 24, 2025 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant