-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
Upcoming Node.js Major Release (v24) #57057
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
Comments
Fixes nodejs#57057 --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/nodejs/node/issues/57057?shareId=XXXX-XXXX-XXXX-XXXX).
I don't know what to do about it but the V8 update (#57114) is still quite far from being ready. |
FYI I will create the v24.x branch tomorrow (2025-03-24) (final cut-off) and we'll amend V8 whenever #57114 is landed. |
Done. Node.js v24 branches have been created. From now on, any new semver-major commit that lands on
|
OpenSSL 3.5 was just published as LTS today. Could it be updated prior to Node 24 so that we can build on the added features between 3.0 and 3.5 for the next major? Or is it better that it only gets updated for Node 25? |
OpenSSL 3.5 is not expected to be semver-major -- we're currently testing with Node.js dynamically linked to it (well the beta but I'll update that when I have time) and it only needed one small test update (to cope with messages from the |
👀 |
This comment has been minimized.
This comment has been minimized.
👀 |
This comment has been minimized.
This comment has been minimized.
Hi folks, We are working on V8 13.6 PR to land Node.js v24. |
Node v24 has been released |
A reminder that the next Node.js SemVer Major release is scheduled for 2025-04-22.
All commits that were landed until 2025-03-22 (one month prior to the release) will be included in the next semver major release. Please ensure that any necessary preparations are made in advance.
For more details on the release process, consult the Node.js Release Working Group repository.
cc: @nodejs/collaborators
The text was updated successfully, but these errors were encountered: