-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
v14.15.5 proposal #37074
v14.15.5 proposal #37074
Conversation
d71b3a9
to
97f1314
Compare
cc: @nodejs/streams as there are a number of streams bug fixes going out in this release. |
Delayed by a couple of CITGM reruns. Will update the changelog dates to tomorrow and aim to promote in the morning. |
97f1314
to
8045a8b
Compare
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.
lgtm
let me know if there is anything in those CITGM I need to take a look for streams.
CITGM is very flaky on both
Summary:
Edit: rewire seems okay on no-build reruns on the rc.0 - https://ci.nodejs.org/job/citgm-smoker-nobuild/nodes=win10-vs2019/1021/console |
Just doing my final testing before release, and I have just noticed @nodejs/npm / @MylesBorins thoughts on how to proceed? Reland #36838 with the version updated to 6.14.11? I think v10.23.2 might have gone out yesterday with the content of npm 6.14.11 but reports npm 6.14.10. |
@BethGriggs it looks like there may have been something that went awry with the upgrade commit. The release commit definitely bumped the version number, and the published version of the package has the right version. We could delay and get a fixed version of the update commit for you. what do you think? |
@MylesBorins, sure, happy to delay this one to patch up the commit. (Also to be updated on v12.x-staging) I'm not sure on the best approach for v10.23.2 though |
@BethGriggs I think we need to see how big the diff is when we get an updated patch. |
Fixes: #36437 PR-URL: #36479 Backport-PR-URL: #36831 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
PR-URL: #36633 Backport-PR-URL: #36940 Fixes: #36620 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Danielle Adams <[email protected]>
PR-URL: #36633 Backport-PR-URL: #36940 Fixes: #36620 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Danielle Adams <[email protected]>
PR-URL: #36618 Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: #37173 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Beth Griggs <[email protected]>
Signed-off-by: Ruben Bridgewater <[email protected]> Backport-PR-URL: #37100 PR-URL: #36178 Fixes: #35730 Fixes: #36151 Refs: #35754 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Guy Bedford <[email protected]> Reviewed-By: James M Snell <[email protected]>
Signed-off-by: Ruben Bridgewater <[email protected]> Backport-PR-URL: #37100 PR-URL: #36178 Fixes: #35730 Fixes: #36151 Refs: #35754 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Guy Bedford <[email protected]> Reviewed-By: James M Snell <[email protected]>
8045a8b
to
a1b41b3
Compare
Original commit message: [wasm] PostMessage of Memory.buffer should throw PostMessage of an ArrayBuffer that is not detachable should result in a DataCloneError. Bug: chromium:1170176, chromium:961059 Change-Id: Ib89bbc10d2b58918067fd1a90365cad10a0db9ec Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2653810 Reviewed-by: Adam Klein <[email protected]> Reviewed-by: Andreas Haas <[email protected]> Commit-Queue: Deepti Gandluri <[email protected]> Cr-Commit-Position: refs/heads/master@{#72415} Refs: v8/v8@dfcf1e8 PR-URL: #37245 Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Vladimir de Turckheim <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Notable changes: - **deps**: - upgrade npm to 6.14.11 (Ruy Adorno) (#37173) - V8: backport dfcf1e86fac0 (Michaël Zasso) (#37245) - Note: Node.js is not believed to be vulnerable to CVE-2021-21148. - **stream,zlib**: do not use \_stream\_\* anymore (Matteo Collina) (#36618) PR-URL: #37074
a1b41b3
to
7b6ab5e
Compare
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.
lgtm
Fixes: #36364 PR-URL: #36410 Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Ricky Zhou <[email protected]>
Notable changes: - **deps**: - upgrade npm to 6.14.11 (Ruy Adorno) (#37173) - V8: backport dfcf1e86fac0 (Michaël Zasso) (#37245) - Note: Node.js is not believed to be vulnerable to CVE-2021-21148. - **stream,zlib**: do not use \_stream\_\* anymore (Matteo Collina) (#36618) PR-URL: #37074
7b6ab5e
to
9fff0d3
Compare
CITGM on v14.15.5 looks okay to me. Pino is failing on all platforms due to a lint failure, which is being addressed as part of pinojs/pino#961 (cc @mcollina) |
thanks, sorry about this. I'll fix asap. |
Release build on 9fff0d3 : https://ci-release.nodejs.org/job/iojs+release/6655 |
Notable changes: - **deps**: - upgrade npm to 6.14.11 (Ruy Adorno) (#37173) - V8: backport dfcf1e86fac0 (Michaël Zasso) (#37245) - Note: Node.js is not believed to be vulnerable to CVE-2021-21148. - **stream,zlib**: do not use \_stream\_\* anymore (Matteo Collina) (#36618) PR-URL: #37074
2021-02-09, Version 14.15.5 'Fermium' (LTS), @BethGriggs
Notable Changes
Commits
20b1e6c802
] - deps: V8: backport dfcf1e86fac0 (Michaël Zasso) #37245408c7a65f3
] - deps: upgrade npm to 6.14.11 (Ruy Adorno) #37173017eed665b
] - http: do not loop over prototype in Agent (Michaël Zasso) #3641025a3204fe2
] - http: don't cork .end when not needed (Dimitris Halatsis) #366332a1e4e9244
] - stream: accept iterable as a valid first argument (ZiJian Liu) #364799ff73fcdbe
] - stream,zlib: do not use _stream_* anymore (Matteo Collina) #36618c03cddb46f
] - test: http complete response after socket double end (Dimitris Halatsis) #36633f206505e9d
] - util: fix instanceof checks with null prototypes during inspection (Ruben Bridgewater) #361782f7944b18b
] - util: fix module prefixes during inspection (Ruben Bridgewater) #36178