Sourced from @​actions/cache's changelog.

6.1.0

• Handle cache write error due to read-only token: detect the cache write denied: prefix on cache reservation failures and surface it as a core.warning (without failing the run).

6.0.1

• Bump dependency versions (#2393):
  • @actions/core to ^3.0.1
  • @actions/http-client to ^4.0.1
  • @actions/io to ^3.0.2
  • @azure/core-rest-pipeline to ^1.23.0
  • @azure/storage-blob to ^12.31.0
  • semver to ^7.7.4

6.0.0

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

5.0.5

• Bump @actions/glob to 0.5.1

5.0.4

• Bump @actions/http-client to 3.0.2

5.0.3

Prevent retries for rate limited cache operations 2243.

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

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

4.1.0

... (truncated)

• See full diff in compare view