Upcoming Release Changes#2406
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
May 9, 2025 16:11
6aec55f to
401e3bb
Compare
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
May 10, 2025 00:29
401e3bb to
e45099c
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
May 10, 2025 12:42
e45099c to
d03a751
Compare
Contributor
Author
✅
|
Contributor
Author
✅
|
Contributor
Author
✅
|
Contributor
Author
✅
|
Contributor
Author
✅
|
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/fetch@0.10.7
Patch Changes
#2383
9527e8fThanks @ardatan! - Some implementations like
compressionnpmpackage do not implement
response.write(data, callback)signature, but whatwg-node/server waitsfor it to finish the response stream. Then it causes the response stream hangs when the
compression package takes the stream over when the response data is larger than its threshold.
It is actually a bug in
compressionpackage;expressjs/compression#46 But since it is a
common mistake, we prefer to workaround this on our end.
Now after calling
response.write, it no longer uses callback but first it checks the result;if it is
true, it means stream is drained and we can callresponse.endimmediately. else if itis
false, it means the stream is not drained yet, so we can wait for thedrainevent to callresponse.end.Updated dependencies
[
9527e8f]:@whatwg-node/node-fetch@0.7.19
Patch Changes
#2383
9527e8fThanks @ardatan! - Some implementations like
compressionnpmpackage do not implement
response.write(data, callback)signature, but whatwg-node/server waitsfor it to finish the response stream. Then it causes the response stream hangs when the
compression package takes the stream over when the response data is larger than its threshold.
It is actually a bug in
compressionpackage;expressjs/compression#46 But since it is a
common mistake, we prefer to workaround this on our end.
Now after calling
response.write, it no longer uses callback but first it checks the result;if it is
true, it means stream is drained and we can callresponse.endimmediately. else if itis
false, it means the stream is not drained yet, so we can wait for thedrainevent to callresponse.end.Updated dependencies
[
d86b4f3]:@whatwg-node/promise-helpers@1.3.2
Patch Changes
d86b4f3Thanks @slagiewka! - Reuse fake promise Symbol
@whatwg-node/server@0.10.6
Patch Changes
#2383
9527e8fThanks @ardatan! - Some implementations like
compressionnpmpackage do not implement
response.write(data, callback)signature, but whatwg-node/server waitsfor it to finish the response stream. Then it causes the response stream hangs when the
compression package takes the stream over when the response data is larger than its threshold.
It is actually a bug in
compressionpackage;expressjs/compression#46 But since it is a
common mistake, we prefer to workaround this on our end.
Now after calling
response.write, it no longer uses callback but first it checks the result;if it is
true, it means stream is drained and we can callresponse.endimmediately. else if itis
false, it means the stream is not drained yet, so we can wait for thedrainevent to callresponse.end.Updated dependencies
[
d86b4f3,9527e8f]:@benchmarks/server@0.0.53
Patch Changes
[
9527e8f]:@e2e/aws-lambda@0.0.41
Patch Changes
[
9527e8f]:@e2e/shared-server@0.0.142
Patch Changes
[
9527e8f]:@e2e/vercel@0.0.142
Patch Changes