Release
Release copied to clipboard
nodejs
Release plan - v18.x Maintenance LTS
Draft schedule - all dates subject to change
| Version | Release Date | Releaser |
|---|---|---|
| v18.12.0 | 2022-10-25 | @ruyadorno and @RafaelGSS (LTS Transition) |
| v18.12.1 | 2022-11-04 | @juanarbol (Security) |
| v18.13.0 | 2023-01-03 | @danielleadams |
| v18.14.0 | 2023-01-31 | @juanarbol |
| v18.14.1 | 2023-02-16 | @juanarbol (Security) |
| v18.14.2 | 2023-02-21 | @MylesBorins |
| v18.15.0 | 2023-03-07 | @juanarbol |
| v18.16.0 | 2023-04-11 | @danielleadams |
| v18.16.1 | 2023-06-20 | @RafaelGSS (Security) |
| v18.17.0 | 2023-08-09 | @danielleadams |
| v18.18.0 | 2023-09-18 | @ruyadorno |
| v18.18.1 | 2023-10-10 | @richardlau |
| v18.18.2 | 2023-10-13 | @RafaelGSS |
| v18.19.0 | 2023-11-29 | @targos |
| v18.19.1 | 2023-02-14 | @RafaelGSS (Security) |
| v18.20.0 | 2024-03-26 | @richardlau |
| v18.20.1 | 2024-04-03 | @RafaelGSS (Security) |
| v18.20.2 | 2024-04-10 | @RafaelGSS (Security) |
| v18.20.3 | 2024-05-21 | @richardlau |
| v18.?.? |
Current
| Version | Release Date | Releaser |
|---|---|---|
| v18.0.0 | 2022-04-19 | @BethGriggs |
| v18.1.0 | 2022-05-03 | @targos |
| v18.2.0 | 2022-05-11 | @BethGriggs prepared by @RafaelGSS |
| v18.3.0 | 2022-05-31 | @bengl |
| v18.4.0 | 2022-06-16 | @danielleadams |
| v18.5.0 | 2022-07-07 | @RafaelGSS (security) |
| v18.6.0 | 2022-07-13 | @targos |
| v18.7.0 | 2022-07-26 | @danielleadams |
| v18.x.x | 2022-08-09 | @danielleadams |
| v18.8.0 | 2022-08-24 | @ruyadorno |
| v18.9.0 | 2022-09-06 | @RafaelGSS |
| v18.9.1 | 2022-09-22 | @RafaelGSS (security) |
| v18.10.0 | 2022-09-28 | @RafaelGSS |
| v18.11.0 | 2022-10-11 | @danielleadams |
@juanarbol do you still plan to prepare a release for tomorrow? No worries if you can't, but I'd like to know so I take time to do it.
@targos do you still have time to pick it up (maybe delayed until Weds/Thurs)? I reached out to @juanarbol by other means and it seems he is unavailable this week.
I'm still preparing v18.x - aiming for Thursday (8/11) release date.
Preparing v18.x is still ongoing - right now, it seems I am blocked by backporting https://github.com/nodejs/node/pull/44056 (I may try myself) because the rest of the merge conflicts/test failures build on top of that. Depending on if I can get that done in the next ~2 days, I may just work with @ruyadorno to get the giant 18.x release out next week for 8/23.
@nodejs/releasers We have a release target of 2022-09-20. However, the Security Release (v18.10.0) will be issued on 2022-09-22. Would be ok to postpone the regular release to at least 2 days after the Security Release (24/09)? That would be better for me since I'm part of both releases.
@RafaelGSS I think we could push it back a week, or even skip this next minor release in favor of the security release. As long as commits from main get pulled in before it goes LTS, I think it's fine.
@RafaelGSS I think we could push it back a week, or even skip this next minor release in favor of the security release. As long as commits from main get pulled in before it goes LTS, I think it's fine.
I can't push it a week, because I won't be able to do any release after 29 (until the middle of Oct). I think I can release it on 27/09 cutting commits from 23/09. What do you think?
@RafaelGSS oh, I see. I think that's fine because the next target date is 04/10. I can also pick it up for 27/09 if you want with all the recent commits, and then we can see if we should push the 04/10 one out 1 week too.
Hi! Will there be a release between now and the LTS version? Would the LTS release actually only contain a version number bump commit?
Can you update the schedule, maybe also with planned releases like the 19 release schedule? I think it's good to know when a release is scheduled, e.g. if you wait for a fix is deployed.
We will probably discuss and update the schedule in our monthly meeting next week.
We will probably discuss and update the schedule in our monthly meeting next week.
I see new version already for node 19, new version of 18 was scheduled for yesterday, so I hope 18.13 will be released soon.
@w3nl That's on me. I didn't get around to releasing this week, but I will have time this upcoming few days to prepare next week's release.
@danielleadams no release yet?
Still waiting on a fix I reported on 15 okt and, fixed on 18 okt and merged to main om 20 okt.
And still not available in the latest 18.x, so I hope the new 18.x will released soon with the fix for the coverage. 18.12.x had only some security fixed, not other bug fixed.
If you need some help, please let it know.
Is it possible to include https://github.com/nodejs/node/pull/45659 in the 18.13 release?
More desired candidates for 18.13.0 that could be a DoS if calls to certificate verification alternate with signing.
https://github.com/nodejs/node/pull/45377 https://github.com/nodejs/node/pull/45495
There will not be a v18.x release in December. I've updated our schedule. The next release is planned for early January. It will include all the fixes mentioned.
hi @juanarbol, just wanted to confirm if you're still available for the next v18 release on January 31st.
hi @juanarbol, just wanted to confirm if you're still available for the next v18 release on January 31st.
Yes! I do
@juanarbol is there any plans to update npm package to 9.4.2 in the next release? My question is related to the remediation of security vulnerability merged in https://github.com/npm/cli/pull/6115 (CVE-2022-25881)
Thanks a lot!
Just in case anyone was interested in my last question, the fix was included in v18.14.2 (PR: https://github.com/nodejs/node/pull/46673 )
I want to offer apologies for the delay in the v18.15.0 release. I updated the release table with the new date (march 7, 2023) while my new keys landed.
Is it possible to include the perf improvements from https://github.com/nodejs/node/pull/46425 in the next v18.x release?
Hello @targos, Do you have plans to upgrade OpenSSL to version 3.0.12 in v18.19.0? I am concerned about whether the following vulnerability will be resolved. https://security.snyk.io/vuln/SNYK-ALPINE317-OPENSSL-6032385
Can we please land https://github.com/nodejs/node/pull/50186 on the upcoming v18?
This is a bug fix. Because of this we are unable to move to node 18 and have to use node 16.
The Node-API team also needs https://github.com/nodejs/node/pull/50991 in v18.x in order to unblock https://github.com/nodejs/node-addon-api/pull/1409. Could you please add it to the upcoming v18 release?
Hi Folks,
Node.js v18 is in maintenance, implying we no longer perform scheduled releases to this release line. However, a release would only happen if one of these criteria is met:
- A nasty bug is encountered
- Security release
- One of @nodejs/releasers decides/wants to perform a release
The suggestion to all Node.js users is to upgrade to Node.js 20 as soon as possible.