Preparation for v18.0.0 #42139

Activity

1. targos

   added

   metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.

   releaseIssues and PRs related to Node.js releases.Issues and PRs related to Node.js releases.

   on Feb 26, 2022
2. aduh95 commented on Feb 26, 2022

   

   aduh95

   on Feb 26, 2022

   Contributor

   More actions

   [ ] 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.

   👀React with 👀1Reacted by Steven
3. richardlau commented on Feb 26, 2022

   

   richardlau

   on Feb 26, 2022

   Member

   More actions

   Should we be using project/milestones for this tracking? (I have no personal preference here.)
4. targos commented on Feb 27, 2022

   

   targos

   on Feb 27, 2022

   MemberAuthor

   More actions

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

   We can't comment/discuss in projects/milestones, though.
5. ShogunPanda commented on Mar 1, 2022

   

   ShogunPanda

   on Mar 1, 2022

   Last edited by ShogunPanda

   Contributor

   More actions

   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
6. BethGriggs commented on Mar 1, 2022

   

   BethGriggs

   on Mar 1, 2022

   Member

   More actions

   @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.

   👍React with 👍2Reacted by Paolo Insogna and lin72h
7. richardlau

   added

   v18.x

   on Apr 11, 2022
8. targos commented on Apr 13, 2022

   

   targos

   on Apr 13, 2022

   MemberAuthor

   More actions

   I think we can close this. Thanks everyone!

   👍React with 👍2Reacted by Beth Griggs and lin72h

   ❤️React with ❤️1Reacted by Alexei Boronine
9. targos

   closed this as completedon Apr 13, 2022