delta/node-new.git, branch v14.15.0-proposal

2020-10-27, Version 14.15.0 'Fermium' (LTS)

2020-10-26T10:34:29+00:00

Notable changes:

This release marks the transition of Node.js 14.x into Long Term Support (LTS)
with the codename 'Fermium'. The 14.x release line now moves into "Active LTS"
and will remain so until October 2021. After that time, it will move into
"Maintenance" until end of life in April 2023.

PR-URL: https://github.com/nodejs/node/pull/35746

doc: add missing link in Node.js 14 Changelog

2020-10-26T10:19:31+00:00

Refs: https://github.com/nodejs/node/pull/35525

PR-URL: https://github.com/nodejs/node/pull/35782
Reviewed-By: Richard Lau 
Reviewed-By: Rich Trott 
Reviewed-By: Gireesh Punathil

doc: fix Node.js 14.x changelogs

2020-10-22T17:51:34+00:00

Remove the table headings for Node.js 13.x that were not removed in
631dd21709.

Vertically align the list of releases in the 14.x changelog as they
are in the changelogs for 12.x and 10.x.

PR-URL: https://github.com/nodejs/node/pull/35756
Reviewed-By: Antoine du Hamel 
Reviewed-By: Beth Griggs 
Reviewed-By: Shelley Vohr 
Reviewed-By: Myles Borins 
Reviewed-By: Michaël Zasso

Revert "test: mark test-webcrypto-encrypt-decrypt-aes flaky"

2020-10-19T20:02:22+00:00

This reverts commit 3d21792f8624d3f8d406700b5a661d7ef9e86f84.

PR-URL: https://github.com/nodejs/node/pull/35666
Reviewed-By: Rich Trott 
Reviewed-By: Daijiro Wachi 
Reviewed-By: Richard Lau 
Reviewed-By: Luigi Pinca

Working on v14.14.1

2020-10-15T23:27:56+00:00

PR-URL: https://github.com/nodejs/node/pull/35648

2020-10-15, Version 14.14.0 (Current)

2020-10-15T23:15:18+00:00

Notable changes:

crypto:
  * update certdata to NSS 3.56 (Shelley Vohr) https://github.com/nodejs/node/pull/35546
doc:
  * add aduh95 to collaborators (Antoine du Hamel) https://github.com/nodejs/node/pull/35542
fs:
  * (SEMVER-MINOR) add rm method (Ian Sutherland) https://github.com/nodejs/node/pull/35494
http:
  * (SEMVER-MINOR) allow passing array of key/val into writeHead (Robert Nagy) https://github.com/nodejs/node/pull/35274
src:
  * (SEMVER-MINOR) expose v8::Isolate setup callbacks (Shelley Vohr) https://github.com/nodejs/node/pull/35512

PR-URL: https://github.com/nodejs/node/pull/35648

stream: multiple stream backports

2020-10-15T19:48:14+00:00

includes:

* stream: simpler and faster Readable async iterator
* stream: don't destroy on async iterator success
* stream: async iterator stop read if destroyed

PR-URL: https://github.com/nodejs/node/pull/34887
Refs: https://github.com/nodejs/node/pull/34035
Refs: https://github.com/nodejs/node/pull/35122
Refs: https://github.com/nodejs/node/pull/35640
Refs: https://github.com/nodejs/node/issues/34680
Reviewed-By: Luigi Pinca 
Reviewed-By: Matteo Collina

module: cjs-module-lexer@0.4.1 big endian fix

2020-10-14T20:24:46+00:00

PR-URL: https://github.com/nodejs/node/pull/35634
Reviewed-By: Richard Lau 
Reviewed-By: Michaël Zasso 
Reviewed-By: Ujjwal Sharma

test: add regression test for v8.getHeapSnapshot() crash

2020-10-14T20:24:46+00:00

Fixes: https://github.com/nodejs/node/issues/35559

PR-URL: https://github.com/nodejs/node/pull/35612
Reviewed-By: Michaël Zasso 
Reviewed-By: Colin Ihrig 
Reviewed-By: Richard Lau 
Reviewed-By: Jiawen Geng 
Reviewed-By: Rich Trott 
Reviewed-By: Gireesh Punathil 
Reviewed-By: Gerhard Stöbich

deps: V8: cherry-pick 3176bfd447a9

2020-10-14T20:24:46+00:00

Original commit message:

    [heap-profiler] Fix crash when a snapshot deleted while taking one

    Fix a crash/hang that occurred when deleting a snapshot during the
    GC that is part of taking another one.

    Specifically, when deleting the only other snapshot in such
    a situation, the `v8::HeapSnapshot::Delete()` method sees that there
    is only one (complete) snapshot at that point, and decides that it is
    okay to perform “delete all snapshots” instead of just deleting
    the requested one. That resets the internal string lookup table
    of the heap profiler, but the new snapshot that is currently in
    progress still holds references to the old string lookup table,
    leading to a use-after-free segfault or infinite loop.

    Fix this by guarding against resetting the string table while
    another heap snapshot is being taken, and add a test that would
    crash before this fix.

    This can be triggered in Node.js by repeatedly calling
    `v8.getHeapSnapshot()`, which provides heap snapshots as weakly
    held host objects.

    Change-Id: If9ac3728bf79114000982f1e7bb05e8034299e3c
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2464823
    Reviewed-by: Ulan Degenbaev 
    Commit-Queue: Ulan Degenbaev 
    Cr-Commit-Position: refs/heads/master@{#70445}

Refs: https://github.com/v8/v8/commit/3176bfd447a909fa9608687fe3eabcf62ec7b2eb

PR-URL: https://github.com/nodejs/node/pull/35612
Refs: https://github.com/nodejs/node/issues/35559
Reviewed-By: Michaël Zasso 
Reviewed-By: Colin Ihrig 
Reviewed-By: Richard Lau 
Reviewed-By: Jiawen Geng 
Reviewed-By: Rich Trott 
Reviewed-By: Gireesh Punathil 
Reviewed-By: Gerhard Stöbich