Skip to content
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

Release plan - v18.x Maintenance LTS #737

Open
BethGriggs opened this issue Apr 9, 2022 · 35 comments
Open

Release plan - v18.x Maintenance LTS #737

BethGriggs opened this issue Apr 9, 2022 · 35 comments

Comments

@BethGriggs
Copy link
Member

BethGriggs commented Apr 9, 2022

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.20.4 2024-07-08 @RafaelGSS (Security)
v18.20.5 2024-11-12 @aduh95
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
@targos
Copy link
Member

targos commented Jul 11, 2022

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

@BethGriggs
Copy link
Member Author

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

@targos
Copy link
Member

targos commented Jul 12, 2022

I'll do it

@danielleadams
Copy link
Contributor

I'm still preparing v18.x - aiming for Thursday (8/11) release date.

@danielleadams
Copy link
Contributor

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 nodejs/node#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.

@ruyadorno
Copy link
Member

Sounds good to me @danielleadams 👍

@RafaelGSS
Copy link
Member

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

@danielleadams
Copy link
Contributor

@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
Copy link
Member

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

@danielleadams
Copy link
Contributor

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

@krk
Copy link

krk commented Oct 11, 2022

Hi! Will there be a release between now and the LTS version? Would the LTS release actually only contain a version number bump commit?

@richardlau richardlau changed the title Release plan - v18.x Current Release plan - v18.x Active LTS Nov 1, 2022
@w3nl
Copy link

w3nl commented Nov 11, 2022

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.

@targos
Copy link
Member

targos commented Nov 11, 2022

We will probably discuss and update the schedule in our monthly meeting next week.

@w3nl
Copy link

w3nl commented Nov 30, 2022

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.

@name-yh2022
Copy link

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

@targos
Copy link
Member

targos commented Nov 15, 2023

Yes, it will be part of it.

jaydenseric added a commit to jaydenseric/next-graphql-react that referenced this issue Nov 21, 2023
TODO: Re-enable these tests in Node.js v18 once the fix for this Node.js test runner bug is published in a v18 release:

nodejs/node#48845

The Node.js v18.19.0 release is scheduled for 2023-11-28:

nodejs/Release#737
@kumarrishav
Copy link

Can we please land nodejs/node#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.

@gabrielschulhof
Copy link

The Node-API team also needs nodejs/node#50991 in v18.x in order to unblock nodejs/node-addon-api#1409. Could you please add it to the upcoming v18 release?

@RafaelGSS
Copy link
Member

RafaelGSS commented Jan 14, 2024

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.

@kumarrishav
Copy link

Now, that we have 18.x security release planned. can we land nodejs/node#50186 on v18 now?

@gabrielschulhof
Copy link

gabrielschulhof commented Feb 19, 2024

Can we please add

to the next 18.x release? It's blocking nodejs/node-addon-api#1409.

Turns out they don't apply cleanly. So, I filed a PR:

nodejs/node#51804

@gabrielschulhof
Copy link

May we please have nodejs/node#51801 in the next release? It will help us with our next Node-API release.

@richardlau
Copy link
Member

It will depend on timing. nodejs/node#51801 needs to go out in a current release first before being eligible for LTS, and usually be in a current release for two weeks. The next current release looks likely to be Node.js 22.0.0.

@nicolo-ribaudo
Copy link

If there will be another minor release of v18.x, it would be very nice to have nodejs/node#52762 included. The patch applies cleanly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests