Skip to content

Commit e3b43c1

Browse files
alexislefebvreosk2Maledong
authored
Releases: add a link to EOL releases (#4710)
* Releases: add a link to EOL releases * Releases: fix the link to EOL Co-authored-by: osk2 <[email protected]> Co-authored-by: Maledong <[email protected]>
1 parent d7d300f commit e3b43c1

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

locale/en/about/releases.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,4 +22,4 @@ schedule-footer: Dates are subject to change.
2222
Major Node.js versions enter _Current_ release status for six months, which gives library authors time to add support for them.
2323
After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use.
2424
_LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.
25-
Production applications should only use _Active LTS_ or _Maintenance LTS_ releases.
25+
Production applications should only use _Active LTS_ or _Maintenance LTS_ releases. A [list of End-of-Life Releases](https://github.com/nodejs/Release/#end-of-life-releases) is maintained by the Node.js Release Working Group.

0 commit comments

Comments
 (0)