Skip to content

feat: update previous releases page to new schedule #8826

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.

Sign up for GitHub

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

Open
araujogui wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −3
Open

feat: update previous releases page to new schedule #8826

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions apps/site/pages/en/about/previous-releases.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,11 +10,11 @@ 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.
_LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.
Comment on lines 10 to 12
Copy link

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The intro text still describes the old odd/even release model (odd versions become unsupported; even versions move to Active LTS). The new schedule (and the updated schedule image) no longer follows this odd/even pattern, so this page’s written description is now inaccurate. Please update the explanation to match the new cadence (e.g., annual April majors, ~6 months Current, LTS promotion in October, and optionally mention the new Alpha period) and remove the odd/even guidance.

Suggested change
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.
_LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.
New major Node.js versions are released annually in April. Before that, a new major version enters an Alpha period to give maintainers and contributors time to prepare for the upcoming release.
After release, a major version enters _Current_ status for approximately six months, which gives library authors time to add support for it.
In October, the release is promoted to _Active LTS_ status and is ready for general use. _LTS_ stands for "long-term support" and typically guarantees that critical bugs will be fixed for a total of 30 months.

Copilot uses AI. Check for mistakes.
Production applications should only use _Active LTS_ or _Maintenance LTS_ releases.
Production applications should only use LTS releases.
Copy link

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency with the rest of the paragraph (which uses emphasized status names like _LTS_ / _Active LTS_), consider formatting “LTS” here as _LTS_ (or otherwise aligning with the terminology used above) so it’s clearly a release status term rather than a generic adjective.

Suggested change
Production applications should only use LTS releases.
Production applications should only use _LTS_ releases.

Copilot uses AI. Check for mistakes.

## Release Schedule

![Releases](https://github.com/nodejs/Release/main/schedule.svg?sanitize=true)
![New Node.js Release Schedule](/static/images/blog/announcements/2026-new-release-schedule.svg)
Copy link

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change updates the schedule image only for the English page, but other localized about/previous-releases.mdx pages still reference the old schedule SVG from github.com/nodejs/Release/.../schedule.svg. That means non-English users will see a different (and likely outdated) schedule. Consider updating the other locale pages to use the new /static/images/blog/announcements/2026-new-release-schedule.svg asset as well, or centralizing the schedule image reference so it can’t drift across locales.

Copilot uses AI. Check for mistakes.

Full details regarding the Node.js release schedule are available [on GitHub](https://github.com/nodejs/release#release-schedule).

Expand Down
2 changes: 1 addition & 1 deletion packages/i18n/src/locales/en.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@
"ltsVersionFeaturesNotice": "Want new features sooner? Get the <link>latest Node.js version</link> instead and try the latest improvements!"
},
"eolAlert": {
"message": "Commercial support for versions past the Maintenance LTS phase is available through our <link>OpenJS Ecosystem Sustainability Program partners</link>"
"message": "Commercial support for versions past the LTS phase is available through our <link>OpenJS Ecosystem Sustainability Program partners</link>"
},
"eolChip": {
"severity": {
Expand Down
Loading