-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Bump @actions/cache to v5.0.0 #1449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This update removes the punycode deprecation warning by updating to a version of @actions/cache that no longer depends on packages using the deprecated punycode module.
Regenerated license files to reflect the updated dependency tree after bumping @actions/cache to v5.0.0. This includes license information for new transitive dependencies and removes licenses for dependencies that are no longer used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR updates the @actions/cache dependency from v4.1.0 to v5.0.0 to eliminate the Node.js punycode deprecation warning that appears in workflow logs. The punycode module has been deprecated in Node.js, and v5.0.0 of @actions/cache removes all transitive dependencies that relied on it by modernizing its dependency tree with updated Azure SDK packages and replacing deprecated libraries with current alternatives.
Key Changes:
- Updated
@actions/cacheto v5.0.0, which includes major version bumps to its internal dependencies (@actions/core,@actions/exec,@actions/http-client,@actions/ioall upgraded to v2.x within its dependency tree) - Replaced deprecated dependencies (
@azure/ms-rest-js,abort-controller,form-data,event-target-shim) with modern alternatives (@azure/core-rest-pipeline,@typespec/ts-http-runtime,agent-base,http-proxy-agent,https-proxy-agent) - Updated documentation to reference
actions/cache@v5in usage examples
Reviewed changes
Copilot reviewed 25 out of 35 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Bumped @actions/cache from ^4.1.0 to ^5.0.0 |
| package-lock.json | Updated lockfile with new @actions/cache v5.0.0 and all transitive dependencies, including nested v2.x versions of @actions packages, upgraded Azure SDK packages (requiring Node.js >=20.0.0, compatible with project's >=24.0.0 requirement), and removal of deprecated packages |
| docs/advanced-usage.md | Updated example usage from actions/cache@v4 to actions/cache@v5 to align with the dependency upgrade |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Mark @actions/http-client v2.2.1 and v3.0.0 as MIT license (correctly identified from LICENSE file content)
|
I should update a couple things first actually |


Summary
This PR bumps
@actions/cachefrom v4.x to v5.0.0.Closes #1364
Why this change is needed
This update resolves the punycode deprecation warning that users are seeing in their workflow logs:
Root Cause
The
punycodemodule was deprecated in Node.js and is scheduled for removal. The previous version of@actions/cache(v4.x) had transitive dependencies that relied on the built-inpunycodemodule, triggering this deprecation warning.The Fix
@actions/cachev5.0.0 updates its dependency tree to use packages that no longer depend on the deprecatedpunycodemodule, eliminating the warning.Changes
@actions/cachefrom^4.0.3to^5.0.0in package.jsonTesting