Blog: Evolving the Node.js Release Schedule#8631
Conversation
- Add "About the Alpha Channel" section explaining: - Target audience (library authors, CI pipelines) - Expectations (no security patches, API may change) - Rationale (feedback loop + V8 updates) - ABI stability noted as TBD - Simplify schedule phases: Alpha → Current → LTS (29 months) - Remove Active LTS / Maintenance distinction - Add Ubuntu release cycle comparison for familiarity - Clean up v26/v27 timelines (remove Maintenance milestone)
- Add comprehensive 10-year schedule table (v27-v36) with Alpha, Release, LTS, and End of Life dates - Clarify that Alpha channel uses only nightly builds (no formal alpha releases, reducing releaser workload) - Link to nodejs.org/download/nightly for early testing - Reorder Timeline section: v26 → v27 → 10-year table
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
👋 Codeowner Review RequestThe following codeowners have been identified for the changed files: Team reviewers: @nodejs/releasers @nodejs/nodejs-website Please review the changes when you have a chance. Thank you! 🙏 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8631 +/- ##
==========================================
+ Coverage 75.10% 75.12% +0.02%
==========================================
Files 104 104
Lines 9162 9167 +5
Branches 315 315
==========================================
+ Hits 6881 6887 +6
+ Misses 2279 2278 -1
Partials 2 2 ☔ View full report in Codecov by Sentry. |
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
RafaelGSS
left a comment
There was a problem hiding this comment.
Despite those changes, I think we need to mention that it's up to the release team to define what the rules will be to ship semver-major commits in alpha versions.
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Show resolved
Hide resolved
Co-authored-by: Filip Skokan <panva.ip@gmail.com> Signed-off-by: Ulises Gascón <ulisesgascongonzalez@gmail.com>
|
Updated publication date to April 2nd |
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Show resolved
Hide resolved
- Fix Alpha duration from 5 to 6 months (Oct-Mar) - Correct LTS duration from 29 to 30 months - Update total support from 35 to 36 months - Update all EOL dates from March to April - Add alpha versioning format example (27.0.0-alpha.1) - Clarify version number alignment wording - Clarify "from first Current release" for total support - Fix grammar: "to not be" → "not to be" - Fix grammar: "may be not included" → "may not be included" - Improve readability by breaking long lines Co-authored-by: Richard Lau <5445507+richardlau@users.noreply.github.com> Co-authored-by: Nick Schonning <1297909+nschonni@users.noreply.github.com>
|
@UlisesGascon any reason to not land that this week or early next week? |
|
(FYI Without a rebase Vercel will continue to fail, however, since building locally works, you can force merge this, though I'd recommend rebasing and using the Queue) |
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Show resolved
Hide resolved
apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md
Show resolved
Hide resolved
Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
…ase-schedule.md Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Preview url: https://nodejs-org-git-fork-ulisesgascon-release-announcement-openjs.vercel.app/en/blog/announcements/evolving-the-nodejs-release-schedule
PUBLICATION DATE: April 2nd
Objective
This is an initial draft of the blog post, intended to collect feedback and iterate until we have a clear plan for communicating the release schedule change.Explain to the users that we are planning a change in the Release Schedule starting on Node@27 and provide context on how the schedule works in general lines and the motivation for this change.
Context
We have been discussing this topic for a while in nodejs/Release#1113, nodejs/Release#953 and at the Collaboration Summit Chesapeake 2025.
The goal of this post is to communicate the change clearly to users as part of the messaging around Node 26.x, since the new plan will take effect starting with Node 27.x. We decided to write this blog post during our last Release WG meeting.