fix(deps): update dependency @actions/cache to v6

[tradeshift-renovate]

This PR contains the following updates:

Package	Type	Update	Change
@actions/cache (source)	dependencies	major	3.3.0 -> 6.0.0

---

Release Notes

actions/toolkit (@​actions/cache)

v6.0.0

• Breaking change: Package is now ESM-only
  • CommonJS consumers must use dynamic import() instead of require()

v5.0.5

• Bump @actions/glob to 0.5.1

v5.0.4

• Bump @actions/http-client to 3.0.2

v5.0.3

Prevent retries for rate limited cache operations 2243.

v5.0.1

• Fix Node.js 24 punycode deprecation warning by updating @azure/storage-blob from ^12.13.0 to ^12.29.1 #​2213
• Newer storage-blob uses @azure/core-rest-pipeline instead of deprecated @azure/core-http, which eliminates the transitive dependency on node-fetch@2 → whatwg-url@5 → tr46@​0.0.3 that used the deprecated punycode module

v5.0.0

• Remove @azure/ms-rest-js dependency #​2197
  • The TransferProgressEvent type is now imported from @azure/core-rest-pipeline instead of @azure/ms-rest-js
• Bump @actions/core from ^1.11.1 to ^2.0.0 #​2198
• Bump @actions/exec from ^1.0.1 to ^2.0.0 #​2198
• Bump @actions/glob from ^0.1.0 to ^0.5.0 #​2198
• Bump @actions/http-client from ^2.1.1 to ^3.0.0 #​2198
• Bump @actions/io from ^1.0.1 to ^2.0.0 #​2198
• Add support for Node.js 24 #​2110
• Add node-fetch override to resolve audit vulnerabilities #​2110

v4.1.0

• Remove client side 10GiB cache size limit check & update twirp client #​2118

v4.0.5

• Reintroduce @​protobuf-ts/runtime-rpc as a runtime dependency #​2113

v4.0.4

⚠️ Faulty patch release. Upgrade to 4.0.5 instead.

• Optimized cache dependencies by moving @protobuf-ts/plugin to dev dependencies #​2106
• Improved cache service availability determination for different cache service versions (v1 and v2) #​2100
• Enhanced server error handling: 5xx HTTP errors are now logged as errors instead of warnings #​2099
• Fixed cache hit logging to properly distinguish between exact key matches and restore key matches #​2101

v4.0.3

• Added masking for Shared Access Signature (SAS) cache entry URLs #​1982
• Improved debugging by logging both the cache version alongside the keys requested when a cache restore fails #​1994

v4.0.2

• Wrap create failures in ReserveCacheError #​1966

v4.0.1

• Remove runtime dependency on twirp-ts #​1947
• Cache miss as debug, not warning annotation #​1954

v4.0.0

Important changes

The cache backend service has been rewritten from the ground up for improved performance and reliability. The @​actions/cache package 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 this release are fully backward compatible.

All previous versions of this package will be deprecated. We recommend upgrading to version 4.0.0 as soon as possible before February 1st, 2025.

If you do not upgrade, all workflow runs using any of the deprecated @​actions/cache packages will fail.

Upgrading to the recommended version should not break or require any changes to your workflows beyond updating your package.json to version 4.0.0.

Read more about the change & access the migration guide: reference to the announcement.

Minor changes

• Update @actions/core to 1.11.0
• Update semver 6.3.1
• Add twirp-ts 2.5.0 to dependencies

---

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: Never, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Renovate Bot.

[tradeshift-renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package.json

Command failed: npm run --if-present package
Error: Module not found: Error: Package path . is not exported from package /tmp/renovate/repos/github/Tradeshift/actions-docker/node_modules/@actions/cache (see exports field in /tmp/renovate/repos/github/Tradeshift/actions-docker/node_modules/@actions/cache/package.json)
Did you mean './@actions/cache'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
    at /tmp/renovate/repos/github/Tradeshift/actions-docker/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:23:2001732
    at /tmp/renovate/repos/github/Tradeshift/actions-docker/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:23:389111
    at _done (eval at create (/tmp/renovate/repos/github/Tradeshift/actions-docker/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:21:81694), <anonymous>:9:1)
    at eval (eval at create (/tmp/renovate/repos/github/Tradeshift/actions-docker/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:21:81694), <anonymous>:34:22)