-
Notifications
You must be signed in to change notification settings - Fork 889
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
Issue v9 release #1947
Issue v9 release #1947
Conversation
@@ -43,6 +43,7 @@ A "month" is defined as 30 consecutive days. | |||
|
|||
| Version | Release Date | End Of LTS Date | Node.js | | |||
| :------ | :----------- | :-------------- | :------------------- | | |||
| 9.x | TBD. | TBD | 18, 20 | | |||
| 8.x | 2022-06-01 | TBD | 14, 16, 18 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 8.x | 2022-06-01 | TBD | 14, 16, 18 | | |
| 8.x | 2022-06-01 | TBD | 14, 16, 18, 20 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'll ship #1930 in a minor and then we can ship this. Ok?
Sounds good. Ship this when you're ready or I'll get to it sometime after work. |
Signed-off-by: Matteo Collina <hello@matteocollina.com>
I'm not seeing a Changelog anywhere for v9? Am I missing something? |
What's the breaking change of v9? |
drop support of Node < latest v18. |
Thanks, came here looking for this info, trying to figure out whether it was safe to upgrade. The release notes state:
Which I found a bit confusing when trying to figure out whether v18 is still supported. |
Once merged and published, the LTS doc needs to be updated with new dates.
I wanted to resolve #1762 before doing this, but it's just too much work for (effectively) two people with a lot else going on. Basically, keeping up with all of the
next
branches and conflicts (I already need to update the work I did a few weeks ago onpino-abstract-transport
) is out of our reach. I have come to the conclusion that we just need to issue v9, and then chip away at #1762. It'll be easier on us.