From ccdfa418747db463a947ba68331f494332ad064a Mon Sep 17 00:00:00 2001 From: Matt Mayer <152770+matthewmayer@users.noreply.github.com> Date: Thu, 7 May 2026 12:26:52 -0400 Subject: [PATCH 1/2] content: Update Node.js release cycle information Clarified the release status of odd and even Node.js versions and updated information on the release cycle starting with Node.js 27. Signed-off-by: Matt Mayer <152770+matthewmayer@users.noreply.github.com> --- apps/site/pages/en/about/previous-releases.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/apps/site/pages/en/about/previous-releases.mdx b/apps/site/pages/en/about/previous-releases.mdx index 01aa12d5e4a59..56e0f8888783b 100644 --- a/apps/site/pages/en/about/previous-releases.mdx +++ b/apps/site/pages/en/about/previous-releases.mdx @@ -8,7 +8,8 @@ layout: about Major Node.js versions enter _Current_ release status for six months, which gives library authors time to add support for them. -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. +Historically (up to Node.js 26), odd-numbered releases (9, 11, etc.) become unsupported after six months, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use. +Starting with Node.js 27, the release cycle will be annual and every major version will move to _Active LTS_ status after its six-month _Current_ phase. _LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use _Active LTS_ or _Maintenance LTS_ releases. From 1ed36481e439ff1dcaeb5dc69e08c86b9869253f Mon Sep 17 00:00:00 2001 From: Matt Mayer <152770+matthewmayer@users.noreply.github.com> Date: Sun, 17 May 2026 08:34:33 +0700 Subject: [PATCH 2/2] Update previous-releases.mdx Co-authored-by: Antoine du Hamel Signed-off-by: Matt Mayer <152770+matthewmayer@users.noreply.github.com> --- apps/site/pages/en/about/previous-releases.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/site/pages/en/about/previous-releases.mdx b/apps/site/pages/en/about/previous-releases.mdx index 56e0f8888783b..83988d91ac758 100644 --- a/apps/site/pages/en/about/previous-releases.mdx +++ b/apps/site/pages/en/about/previous-releases.mdx @@ -9,7 +9,7 @@ layout: about Major Node.js versions enter _Current_ release status for six months, which gives library authors time to add support for them. Historically (up to Node.js 26), odd-numbered releases (9, 11, etc.) become unsupported after six months, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use. -Starting with Node.js 27, the release cycle will be annual and every major version will move to _Active LTS_ status after its six-month _Current_ phase. +Starting with Node.js 27, the release cycle will be annual and every major version will move to _LTS_ status after its six-month _Current_ phase (and six additional months of _Alpha_ phase). _LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use _Active LTS_ or _Maintenance LTS_ releases.