Preparation for v18.0.0

[targos]

Node.js v18.0.0 is scheduled for 2022-04-19. Let's review what needs to be done before then (semver-major changes, adapt CI, etc.)!

• lib: enable global WebCrypto by default #42083
• Platform requirements for Node.js 18 build#2815
  • ansible: add RHEL 8 (initially s390x) build#2859
  • ansible: add RHEL 8 x64 instances build#2886
  • ansible: add ppc64le RHEL 8 instances build#2890
  • build: bump macOS deployment target to 10.15 #42292
  • ansible: updates for Linux arm64 build#2910
  • ansible: arm cross compiler updates for Node.js 18 build#2912
  • doc: update AIX minimum supported arch #42604
  • doc: update minimum glibc requirements for Linux #42659
• V8 update (version 10.1, if possible)
  • ansible: add httplib2 build#2881
  • jenkins: temporarily exclude win32 for Node.js 18 build#2921
• child_process/promises (if possible, @aduh95 is working on it)
• stream: expose web streams globals, remove runtime experimental warning #42225
• Breaking changes to crypto/TLS to follow-up on January 2022 security releases
  • tls: move tls.parseCertString to end-of-life #41479
  • tls: represent registeredID numerically always #41561
  • crypto: change default check(Host|Email) behavior #41600
  • crypto: use RFC2253 format in PrintGeneralName #42002
  • crypto: prettify othername in PrintGeneralName #42123
  • crypto: fix X509Certificate toLegacyObject #42124
• promote: add expected assets for Nodejs 18 build#2922
• ??? (feel free to edit the list or suggest items)

[aduh95]

[ ] lib: enable global WebCrypto by default #42083

This was discussed in the last TSC meeting, it's unlikely to happen in v18.x due to global.crypto already set when using --print (e.g. node -p 'crypto.randomBytes(16).toString("hex")'). The current plan is:

1. Expose a new global proxy to access core modules when using -p or -e flags in v17.x (lib: expose a global node proxy in eval script and REPL #42114).
2. Runtime deprecate global access to node core modules in v18.x
3. Remove global access to core modules in v19.x – then we can enable global WebCrypto by default.

[richardlau]

Should we be using project/milestones for this tracking? (I have no personal preference here.)

[targos]

Should we be using project/milestones for this tracking? (I have no personal preference here.)

We can't comment/discuss in projects/milestones, though.

[ShogunPanda]

I have couple of PRs which would be semver-major.
When is the deadline for this to be merged and eventually included in 18?

• http: make TCP noDelay enabled by default #42163
• http: refactor headersTimeout and requestTimeout logic #41263

[BethGriggs]

@ShogunPanda, if they land on master by 2022-04-12, they should make it into the release (assuming no objections too).

Refs:

Approximately two months before a major release, new vN.x and vN.x-staging branches (where N indicates the major release) should be created as forks of the master branch. Up until one week before the release date, these must be kept in sync with master.

[targos]

I think we can close this. Thanks everyone!