Sourced from actions/cache's releases.
v4.3.0
What's Changed
- Add note on runner versions by
@GhadimiR
in actions/cache#1642- Prepare
v4.3.0
release by@Link
- in actions/cache#1655New Contributors
@GhadimiR
made their first contribution in actions/cache#1642Full Changelog: https://github.com/actions/cache/compare/v4...v4.3.0
Sourced from actions/cache's changelog.
Releases
4.3.0
- Bump
@actions/cache
to v4.1.04.2.4
- Bump
@actions/cache
to v4.0.54.2.3
- Bump
@actions/cache
to v4.0.3 (obfuscates SAS token in debug logs for cache entries)4.2.2
- Bump
@actions/cache
to v4.0.24.2.1
- Bump
@actions/cache
to v4.0.14.2.0
TLDR; 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
orv3
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
orv3.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.
4.1.2
- Add GitHub Enterprise Cloud instances hostname filters to inform API endpoint choices - #1474
- Security fix: Bump braces from 3.0.2 to 3.0.3 - #1475
4.1.1
- Restore original behavior of
cache-hit
output - #14674.1.0
... (truncated)