You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I don't know what to do about it but the V8 update (#57114) is still quite far from being ready.
I think we should postpone the release indefinitely until it is. We can't go on with an LTS release line without it.
Reacted by Ulises Gascón, Sebastian Beltran, Leon Sorokin, Marco Ippolito, Chengzhong Wu, Ruben Bridgewater, Matteo Collina, Dario Piotrowicz, Gürgün Dayıoğlu and Kirill Groshkov
Done. Node.js v24 branches have been created. From now on, any new semver-major commit that lands on main will not go to the Node.js v24 release line (except for V8, obviously).
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 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 openssl-cli application changing). So for now the expectation is that we'll be able to update to OpenSSL 3.5 in Node.js 24 and 22 before it reaches End-of-Life and there's no need to rush it for Node.js 24 (where the cut off has passed).
Reacted by Hannes Hultergård, Brian Evans, Sebastian Barrenechea, Charlie, Jakub Gilis, Allan Hvam, David Fiala, Samuel Murray, Dan Crews, Andrey Briginets and 8 more
Reacted by Konstantin Nesterov, Zachary Milonas-Zdziarski, Raphael Rösch, TÖRÖK Attila, Jose G, Thomas Trapp, nanou, Luke , Derek Dahmer, Mikael Söderström and 8 more
Reacted by Simon Kurtz, Terence, nanou, Luke , Oleg Kislitsyn, Sterling Camden, CogitoBurrito, Jimmy Chen, Mohammed El Amine Larabi, Andrei Lahunou and 4 more
Reacted by TÖRÖK Attila, Emanuele Bellini, Amr Gad, Gabriel R. Barbosa, Daniel Osvaldo Rahmanto, Ali Kehel, Evert De Spiegeleer, Marek Lukáš and Mert Can Altin
Activity
Prepare for Node.js v24 release
targos commentedon Mar 15, 2025
I don't know what to do about it but the V8 update (#57114) is still quite far from being ready.
I think we should postpone the release indefinitely until it is. We can't go on with an LTS release line without it.
RafaelGSS commentedon Mar 23, 2025
FYI I will create the v24.x branch tomorrow (2025-03-24) (final cut-off) and we'll amend V8 whenever #57114 is landed.
RafaelGSS commentedon Mar 24, 2025
Done. Node.js v24 branches have been created. From now on, any new semver-major commit that lands on
mainwill not go to the Node.js v24 release line (except for V8, obviously).ranisalt commentedon Apr 8, 2025
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?
richardlau commentedon Apr 8, 2025
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
openssl-cliapplication changing). So for now the expectation is that we'll be able to update to OpenSSL 3.5 in Node.js 24 and 22 before it reaches End-of-Life and there's no need to rush it for Node.js 24 (where the cut off has passed).gabrielrbarbosa commentedon Apr 22, 2025
👀
alphaleadership commentedon Apr 22, 2025
kevin-appelt commentedon Apr 24, 2025
👀
alphaleadership commentedon Apr 24, 2025
RafaelGSS commentedon Apr 29, 2025
Hi folks,
We are working on V8 13.6 PR to land Node.js v24.
marco-ippolito commentedon May 7, 2025
Node v24 has been released