For a decade, Node.js ran a simple rule: even version numbers were stable, odd ones were experimental. That rule is now history. On March 10, 2026, the Node.js project announced on its official blog one of the biggest structural changes in its history, and Node.js 27 will be the first release line to run entirely under the new rules. Instead of two major releases a year, there will be only one. Instead of experimental in-between versions, there’s now an Alpha channel. And every new major version automatically becomes a Long-Term Support release. For web developers, backend teams, and anyone running Node.js in production, this is not a footnote — it changes when upgrades become due, how long support windows last, and how teams need to structure their maintenance planning.
Table of Contents
Key Takeaways
- Starting October 2026, a new model applies: only one major release per year, shipping in April, with LTS promotion in October.
- The old split between even (LTS-capable) and odd (experimental) version numbers disappears completely.
- Every future major version automatically becomes an LTS release — Node.js 27 is the first version built on this principle.
- A new six-month Alpha channel (October to March) allows breaking changes before the stable “Current” phase begins in April.
- Total support duration per version is now 36 months: six months as Current, plus 30 months as LTS.
What actually changes with the new Node.js release model
Until now, Node.js followed a two-track system. An odd version shipped every April with newer, sometimes experimental features; that line ran for only six months and was never promoted to LTS. Then in October, the even version arrived, moved into Active LTS status after six months, and was maintained for years afterward. Developers had to remember which number was “safe” to use and which wasn’t. That system is being retired entirely. The new model has only one line per year: every major version ships in April, runs for six months as the “Current” release, and is automatically promoted to LTS status in October. There’s no second, competing version fighting for attention anymore.
The new Alpha channel
To give experimental work a home, Node.js is introducing an Alpha channel. It runs for six months, from October to March, and is explicitly the place where breaking changes — semver-major changes — are allowed. Only once the “Current” phase starts in April is a version considered stable enough for production use. For Node.js 27 specifically, that means: the Alpha channel starts on October 28, 2026, ahead of the actual 27.0.0 release in April 2027.
Automatic LTS promotion for every version
The most important point: there’s no longer a version that stays “merely experimental.” Every major version that launches in April automatically receives LTS status the following October. Node.js 27 is the first release built entirely on this principle, setting the template for every major version that follows.
Timeline overview: from Node.js 24 to Node.js 26 to Node.js 27
The transition doesn’t just affect future versions — it runs in parallel with existing, already-active release lines. Three versions matter here in particular:
| Version | Status / Milestone | Date |
|---|---|---|
| Node.js 24 | Moves from Active LTS to Maintenance | October 20, 2026 |
| Node.js 26 | LTS promotion (last version under the old model) | October 28, 2026 |
| Node.js 26 | End of Life | April 2029 |
| Node.js 27 | Alpha channel begins (first version under the new model) | October 28, 2026 |
| Node.js 27 | Release 27.0.0 (Current phase begins) | April 2027 |
| Node.js 27 | LTS promotion | October 2027 |
| Node.js 27 | End of Life | April 2030 |
Node.js 26 plays a special role here: it’s the last version to run completely under the old scheme. Released in April 2026, it gets promoted to LTS on October 28, 2026, moves into maintenance in October 2027, and reaches end of life in April 2029. Node.js 24, meanwhile, already shifts from active maintenance into pure maintenance mode on October 20, 2026 — a routine step that was due regardless of the release-cycle overhaul. In parallel, the Alpha channel for Node.js 27 begins on October 28, 2026 — the exact same day Node.js 26 is promoted to LTS. That overlap marks the real handover point between the old and new models.
Why Node.js is overhauling its release cycle now
The official blog post, “Evolving the Node.js Release Schedule,” cites three main reasons the previous system had reached its limits. First: the odd, experimental releases saw little real-world adoption. Most developers simply waited for the next even-numbered version with LTS prospects rather than committing to a line that was never meant to have long-term support in the first place. Second: the even/odd distinction created constant confusion for newcomers, who had to learn which number counted as “stable” — unnecessary friction that a single, predictable annual rhythm removes. Third, and arguably the most significant: maintaining multiple parallel release lines had become increasingly hard to sustain for the Node.js Release Working Group. The team works largely as volunteers, and every additional active version line means more backports, more security patches, and more coordination overhead. A single yearly rhythm substantially reduces that load without users losing stability or support.
Node.js 27 release cycle in practice: what teams should do now
For development teams running Node.js in production, the change creates concrete action items. Importantly, total support duration remains stable at 36 months per version (six months Current plus 30 months LTS) — what changes is mainly the rhythm in which new versions appear and how reliably they can be planned as LTS. These steps help prepare for the new cycle:
- Keep an eye on Node.js 24: once it moves into maintenance on October 20, 2026, it only receives critical fixes. Teams actively developing on it should plan an upgrade path.
- Treat Node.js 26 as a transition version: as the last release under the old model, Node.js 26 stays supported until April 2029 — a solid choice for projects not ready to adopt the new cycle immediately.
- Watch the Node.js 27 Alpha channel, don’t run it in production: from October 28, 2026, the Alpha channel can be used to experiment early with upcoming breaking changes — but strictly in test and staging environments.
- Anchor the release calendar in your CI/CD process: since every future major version ships in April and automatically becomes LTS in October, update planning can finally sync to a fixed, predictable annual rhythm.
- Align dependency pipelines with the new rhythm: package management, Docker images, and build pipelines should be configured to reflect the annual April-October cadence automatically, rather than continuing to filter by even-numbered versions.
For DevOps teams, this mainly means one thing: less decision complexity. Since every major version inevitably becomes LTS, the question of whether a new Node release is even “LTS-worthy” disappears. The answer going forward is always: yes, automatically, after six months.
How much Node.js actually gains or loses against alternatives in day-to-day server workloads is a separate question worth tracking — our PHP Swoole benchmark comparing PHP, Node.js, and Go takes a closer look at exactly that.
Conclusion
The Node.js 27 release cycle marks a clear break with more than a decade of established practice. Instead of two competing version lines, there’s now a single, plannable annual rhythm: an Alpha phase in the fall, a stable launch in April, automatic LTS promotion in October. Node.js 26 closes the old chapter as the last version under the previous model, while Node.js 27 sets the tone for every future release as the first version of the new one. For developers and teams, now is a good moment for a quick reality check: when does your current Node.js version fall out of support? Does it make sense to move to Node.js 26 as an intermediate step? And should your own release calendar already shift toward the new April-October cadence? Answering these questions early avoids scrambling when Node.js 27.0.0, the first release of the new era, arrives in April 2027.
