Repository navigation
Upcoming Release Changes - #3685
Merged
Merged
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
force-pushed
the
changeset-release/master
branch
2 times, most recently
from
October 15, 2026 23:41
816285f to
37b9c99
Compare
Contributor
Author
🚀 Snapshot Release (
|
| Package | Version | Info |
|---|---|---|
@whatwg-node/server |
0.13.1-rc-20261016084928-37b9c99ead24898b1677924f2ac0e2537e42734d |
npm ↗︎ unpkg ↗︎ |
@whatwg-node/server |
0.13.1-rc-20261016084928-37b9c99ead24898b1677924f2ac0e2537e42734d |
npm ↗︎ unpkg ↗︎ |
Contributor
Author
✅
|
Contributor
Author
✅
|
Contributor
Author
✅
|
Contributor
Author
✅
|
Contributor
Author
✅
|
Contributor
Author
✅
|
Contributor
Author
✅
|
github-actions
Bot
force-pushed
the
changeset-release/master
branch
19 times, most recently
from
October 20, 2026 18:31
9d373aa to
9f6b4c1
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
7 times, most recently
from
October 22, 2026 20:12
ae601fa to
53e08d5
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
October 22, 2026 20:13
53e08d5 to
e409795
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@whatwg-node/node-fetch@0.9.2
Patch Changes
#3694
f927bd2Thanks @dependabot! - dependencies
updates:
@fastify/busboy@^3.2.3↗︎(from
^3.1.1, independencies)#3715
06e7013Thanks @ardatan! - Fulfill pending
reader.read()as{ done: true }whencancel(reason)runs, matching theWHATWG ReadableStream cancel algorithm (and native undici).
Previously
cancel()calledreadable.destroy()without ending the streamfirst, so an in-flight
read()rejected withERR_STREAM_PREMATURE_CLOSE/Premature closeinstead of settling as done. The cancelreasonstillreaches
underlyingSource.cancel(reason).@whatwg-node/server@0.13.1
Patch Changes
#3672
978ebedThanks @renovate! - Drain unread request
bodies correctly when the adapter uses the platform (native undici)
Requeston Node.js HTTPS.
discardUnreadNodeRequestBodypreviously only calledIncomingMessage#resume(). That is enough for the@whatwg-node/node-fetchponyfill and for plain
node:http, but native undici keeps an unusedIncomingMessagebody paused. Onnode:httpsthe TLS upload then stallsmid-response:
readableFlowingstays false, buffered unread bytes remain, andkeep-alive / early-response paths hang or fail Node 26 unit coverage
(
discard-unread-request-body).For
fetchAPI.Request === globalThis.Requeston HTTPS(
socket.encrypted),normalizeNodeRequestwraps the socket stream in aplatform
ReadableStream(viafetchAPI.ReadableStream). Listeners attach onfirst pull; discard runs a sync drain helper (detach +
IncomingMessage#resume) instead ofbody.cancel(), so unread TLS bytesdrain without destroying keep-alive and without a runtime
node:stream/PassThroughimport or a floating cancel promise. Plain HTTP and ponyfillpaths are unchanged (
IncomingMessage+resume()only). Paths that reuserequest.bodyas the response body still skip discard via the existingidentity checks.
#3717
02e1834Thanks @ardatan! - Pick the native Fetch API for
Requestsubclasses and proxies of them, such as Next.jsNextRequest.Constructor identity treated those requests as the ponyfill, so
useLimitRequestBodySizepiped a native body throughPonyfillTransformStreamand Node threwThe "transform.readable" property must be an instance of ReadableStream.