Skip to content

chore(js-sdk): bump undici to ^7.29.0 and optional undici8 to 8.10.0 #1645

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

Open
mishushakov wants to merge 2 commits into
base: main
Choose a base branch
from
+20 −13
Open

chore(js-sdk): bump undici to ^7.29.0 and optional undici8 to 8.10.0 #1645

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
390f1ba
chore(js-sdk): bump optional `undici8` to 8.10.0
mishushakov Aug 6, 2026
60cd07f
chore(js-sdk): bump `undici` to ^7.29.0 for the security advisories
mishushakov Aug 6, 2026
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
5 changes: 5 additions & 0 deletions .changeset/bump-undici8-8-10-0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'e2b': patch
---

Bump both undici dependencies past the 2026-07-24 security advisories: the required `undici` from `^7.28.0` to `^7.29.0`, and the optional `undici8` (`npm:undici@…`) from 8.8.0 to 8.10.0. Both releases fix one High ([GHSA-4cwx-7wf7-3272](https://github.com/nodejs/undici/security/advisories/GHSA-4cwx-7wf7-3272)) and four Medium advisories, and undici 8.10.0 additionally fixes HTTP/2 request settling, refused-stream retries and GOAWAY handling, which the SDK exercises because every dispatcher it builds sets `allowH2: true`. Neither bump moves a Node floor — 7.29.0 still requires Node `>=20.18.1` and 8.10.0 still requires `>=22.19.0`, matching the `UNDICI_8_MIN_NODE` gate — so package selection and behaviour are unchanged.
1 change: 1 addition & 0 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,7 @@
"minimatch@>=5.0.0 <5.1.8": "^5.1.8",
"minimatch@>=9.0.0 <9.0.7": "^9.0.7",
"minimatch@>=10.0.0 <10.2.3": "^10.2.3",
"undici@>=7.0.0 <7.29.0": "^7.29.0",
"ws@>=8.0.0 <8.20.1": "^8.20.1",
"shell-quote@<1.9.0": "^1.9.0",
"sharp@<0.35.0": "^0.35.0",
Expand Down
4 changes: 2 additions & 2 deletions packages/js-sdk/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,10 +102,10 @@
"openapi-fetch": "^0.14.1",
"platform": "^1.3.6",
"tar": "^7.5.19",
"undici": "^7.28.0"
"undici": "^7.29.0"
},
"optionalDependencies": {
"undici8": "npm:undici@8.8.0"
"undici8": "npm:undici@8.10.0"

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 6, 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 Bump the 7.x undici dependency as well

Because getUndiciPackageCandidates() uses only undici on supported Node versions below 22.19.0, this security bump still leaves Node 20 and Node 22.0–22.18 callers on the unchanged undici range/lock (^7.28.0 / 7.28.0). The same advisory this change is picking up affects undici >=7.0.0 <7.29.0 as well as 8.x (GHSA-4cwx-7wf7-3272), so apps with an existing lockfile at 7.28.0 can upgrade the SDK and still exercise the vulnerable fetch path; raise the 7.x minimum and lockfile to 7.29.0 too.

Useful? React with 👍 / 👎.

},
"engines": {
"node": ">=20.18.1 <21 || >=22"
Expand Down
23 changes: 12 additions & 11 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.