Skip to content

net - chore: upgrade undici to 8 (breaking) #1682

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.

Sign up for GitHub

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

Merged
jaredwray merged 1 commit into from
Jul 8, 2026
+9 −9
Merged

net - chore: upgrade undici to 8 (breaking) #1682

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/net/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@
"cacheable": "workspace:^",
"hookified": "^3.0.1",
"http-cache-semantics": "^4.2.0",
"undici": "^7.24.5"
"undici": "^8.6.0"

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 8, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Surface the transitive Node 22.19 requirement

With this dependency bump, the lockfile resolves undici@8.6.0 with engines: { node: '>=22.19.0' }, while @cacheable/net still declares no engines field. Projects installing @cacheable/net on Node 20 or Node 22.18 with engine-strict package managers can now fail during install even though this package does not advertise the new runtime floor; either keep the dependency on the Node-20-compatible undici line or add the matching engine requirement so consumers get a clear supported runtime.

Useful? React with 👍 / 👎.

},
"keywords": [
"cacheable",
Expand Down
16 changes: 8 additions & 8 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.