Skip to content
This repository has been archived by the owner on Dec 8, 2024. It is now read-only.

chore(deps): update actions/cache action to v4 #42

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 8, 2024

This PR contains the following updates:

Package Type Update Change
actions/cache action major v1.2.0 -> v4.2.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

actions/cache (actions/cache)

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...v4.2.0

v4.1.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v4...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

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.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...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
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. (https://github.com/actions/cache/issues/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

v2.1.6

Compare Source

v2.1.5

Compare Source

v2.1.4

Compare Source

  • Make caching more verbose #​650
  • Use GNU tar on macOS if available #​701

v2.1.3

Compare Source

  • Upgrades @actions/core to v1.2.6 for CVE-2020-15228. This action was not using the affected methods.
  • Fix error handling in uploadChunk where 400-level errors were not being detected and handled correctly

v2.1.2

Compare Source

  • Adds input to limit the chunk upload size, useful for self-hosted runners with slower upload speeds
  • No-op when executing on GHES

v2.1.1

Compare Source

  • Update @actions/cache package to v1.0.2 which allows cache action to use posix format when taring files.

v2.1.0

Compare Source

  • Replaces the http-client with the Azure Storage SDK for NodeJS when downloading cache content from Azure. This should help improve download performance and reliability as the SDK downloads files in 4 MB chunks, which can be parallelized and retried independently
  • Display download progress and speed

v2.0.0

Compare Source

Initial v2 release

What's new in v2

v1.2.1: 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@v1 won't see deprecation warning message.


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 becomes conflicted, 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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants