chore(deps): update actions/cache action to v6 by renovate[bot] · Pull Request #60 · yaytrade/nova-comments

Add release instructions and update maintainer docs by @Link- in #1696
Potential fix for code scanning alert no. 52: Workflow does not contain permissions by @Link- in #1697
Fix workflow permissions and cleanup workflow names / formatting by @Link- in #1699
docs: Update examples to use the latest version by @XZTDean in #1690
Fix proxy integration tests by @Link- in #1701
Fix cache key in examples.md for bun.lock by @RyPeck in #1722
Update dependencies & patch security vulnerabilities by @Link- in #1738

New Contributors

@XZTDean made their first contribution in #1690
@RyPeck made their first contribution in #1722

Full Changelog: actions/cache@v5...v5.0.4

`v5.0.3`

Compare Source

What's Changed

Bump @actions/cache to v5.0.5 (Resolves: https://github.com/actions/cache/security/dependabot/33)
Bump @actions/core to v2.0.3

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

[!IMPORTANT]
actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.

v5.0.1

What's Changed

fix: update @actions/cache for Node.js 24 punycode deprecation by @salmanmkc in #1685
prepare release v5.0.1 by @salmanmkc in #1686

v5.0.0

What's Changed

Upgrade to use node24 by @salmanmkc in #1630
Prepare v5.0.0 release by @salmanmkc in #1684

Full Changelog: actions/cache@v5...v5.0.1

`v5.0.0`

Compare Source

[!IMPORTANT]
actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.

What's Changed

Upgrade to use node24 by @salmanmkc in #1630
Prepare v5.0.0 release by @salmanmkc in #1684

Full Changelog: actions/cache@v4.3.0...v5.0.0

`v4.3.0`

Compare Source

What's Changed

Add note on runner versions by @GhadimiR in #1642
Prepare v4.3.0 release by @Link- in #1655

New Contributors

@GhadimiR made their first contribution in #1642

Full Changelog: actions/cache@v4...v4.3.0

`v4.2.4`

Compare Source

What's Changed

Update README.md by @nebuk89 in #1620
Upgrade @actions/cache to 4.0.5 and move @protobuf-ts/plugin to dev depdencies by @Link- in #1634
Prepare release 4.2.4 by @Link- in #1636

New Contributors

@nebuk89 made their first contribution in #1620

Full Changelog: actions/cache@v4...v4.2.4

`v4.2.3`

Compare Source

What's Changed

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)

New Contributors

@salmanmkc made their first contribution in #1577

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.

Bump @actions/cache to v4.0.2 by @robherley in #1560

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.

docs: GitHub is spelled incorrectly in caching-strategies.md by @janco-absa in #1526
docs: Make the "always save prime numbers" example more clear by @Tobbe in #1525
Update force deletion docs due a recent deprecation by @sebbalex in #1500
Bump @actions/cache to v4.0.1 by @robherley in #1554

New Contributors

@janco-absa made their first contribution in #1526
@Tobbe made their first contribution in #1525
@sebbalex made their first contribution in #1500

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.