fix(cache): update @azure/storage-blob to fix Node.js 24 punycode deprecation #2213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the
@azure/storage-blobdependency in@actions/cacheto fix the punycode deprecation warning in Node.js 24.Problem
The previous dependency chain caused a deprecation warning in Node.js 24:
Node.js 24 deprecates the built-in
punycodemodule, causing warnings when running actions.Solution
@azure/storage-blobfrom^12.13.0to^12.29.1The newer
@azure/[email protected]+uses@azure/core-rest-pipelineinstead of the deprecated@azure/core-http, which eliminates the problematic dependency chain entirely. The@actions/cachepackage already had@azure/core-rest-pipelineas a direct dependency, so this change aligns the storage-blob version with the modern Azure SDK approach.Testing
npm ls tr46returns empty (punycode dep removed)npm ls @azure/core-httpreturns emptyRelated