blog: announce shortening of Node.js 16 lifecycle#4629
Merged
3 commits merged intonodejs:mainfrom Jun 11, 2022
Merged
Conversation
richardlau
commented
Jun 1, 2022
| @@ -0,0 +1,22 @@ | |||
| --- | |||
| date: 2022-06-08T16:00:00Z | |||
Member
Author
There was a problem hiding this comment.
I picked some arbitrary date (a week from now) to give some time for reviews. In my opinion the publish date is flexible as long as it is within the next few weeks.
Member
Author
|
Pushed an update to fix the linter and add a banner for this. |
nschonni
approved these changes
Jun 1, 2022
juanarbol
approved these changes
Jun 1, 2022
trivikr
reviewed
Jun 1, 2022
tniessen
approved these changes
Jun 1, 2022
RafaelGSS
approved these changes
Jun 2, 2022
RaisinTen
approved these changes
Jun 2, 2022
trivikr
approved these changes
Jun 2, 2022
everett1992
reviewed
Jun 2, 2022
juanarbol
approved these changes
Jun 6, 2022
Trott
reviewed
Jun 6, 2022
Trott
reviewed
Jun 6, 2022
|
|
||
| # Bringing forward the End-of-Life Date for Node.js 16 to September 11th, 2023 | ||
|
|
||
| **tl;dr:** we're planning to bring forward the End-of-Life date of Node.js 16 by seven months to coincide with the end of support of OpenSSL 1.1.1 on September 11th, 2023. |
Member
There was a problem hiding this comment.
Suggested change
| **tl;dr:** we're planning to bring forward the End-of-Life date of Node.js 16 by seven months to coincide with the end of support of OpenSSL 1.1.1 on September 11th, 2023. | |
| We are moving the End-of-Life date of Node.js 16 by seven months to coincide with the end of support of OpenSSL 1.1.1 on September 11th, 2023. |
Member
Author
There was a problem hiding this comment.
I've put a "Summary" heading on this sentence (and dropped the "tl;dr".
Trott
reviewed
Jun 6, 2022
Trott
reviewed
Jun 6, 2022
|
|
||
| When we put together Node.js 16 the hope was that we would be able to include OpenSSL 3. Unfortunately the timing of the releases did not allow that to be possible, and we released Node.js 16 with OpenSSL 1.1.1. OpenSSL 1.1.1 is [scheduled to be supported up until September 11th, 2023](https://www.openssl.org/policies/releasestrat.html), which is seven months before the planned End-of-Life date of Node.js 16 (April 2024). | ||
|
|
||
| The project has evaluated the following options: |
Member
There was a problem hiding this comment.
Suggested change
| The project has evaluated the following options: | |
| We have evaluated the following options: |
Trott
reviewed
Jun 6, 2022
Trott
reviewed
Jun 6, 2022
Trott
approved these changes
Jun 6, 2022
danielleadams
approved these changes
Jun 6, 2022
ghost
merged commit 
ghost
mentioned this pull request
Trott
pushed a commit
that referenced
this pull request
Jun 12, 2022
Refs: #4629 Co-authored-by: Maledong <[email protected]>
richardlau
added a commit
to richardlau/Release
that referenced
this pull request
Jun 13, 2022
Update schedule, README table and chart to reflect the change to Node.js 16's End-of-Life date to September 11, 2023. Move Node.js 17 to End-of-Life table. Refs: nodejs/TSC#1222 Refs: nodejs/nodejs.org#4629
Member
Author
richardlau
added a commit
to nodejs/Release
that referenced
this pull request
Jun 15, 2022
Update schedule, README table and chart to reflect the change to Node.js 16's End-of-Life date to September 11, 2023. Move Node.js 17 to End-of-Life table. Refs: nodejs/TSC#1222 Refs: nodejs/nodejs.org#4629
Soufiane88216
added a commit
to Soufiane88216/Release
that referenced
this pull request
Jan 30, 2025
Update schedule, README table and chart to reflect the change to Node.js 16's End-of-Life date to September 11, 2023. Move Node.js 17 to End-of-Life table. Refs: nodejs/TSC#1222 Refs: nodejs/nodejs.org#4629
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs: nodejs/TSC#1222
cc @nodejs/tsc @nodejs/crypto @nodejs/releasers