Node.js 27 Alpha Kicks Off a New Annual Release Model

Node.js is changing how it ships, and the first release under the new system is already here. Node.js 27.0.0-alpha.0.0.0 shipped on October 29, 2026, marking the transition to a new annual-release model that eliminates the old odd/even split between Current and Long-Term Support lines. From Node 27 onward, there will be one major release per year, and every line becomes LTS.

For developers who have lived through years of deciding whether to track Current or wait for LTS, this is a simplification with real consequences. It also comes with breaking changes that library authors should test against now, not in April.

What is in the Node.js 27 alpha

The alpha packs significant upgrades. It includes V8 15.6.75.13, the JavaScript engine at the heart of Node, and a crypto overhaul built on OpenSSL 4.1.0. Cryptography changes are the kind of update that sounds boring and breaks things quietly, because libraries and applications that depend on specific crypto behavior may need adjustments.

Alongside the upgrades, the alpha carries a spread of breaking changes. That is expected for an alpha, and it is the point of the channel: surface the breaks early, while there is still time to fix them before the stable release. Library authors, framework maintainers, and anyone with native add-ons should be testing now. Waiting until the stable release to discover a break is how release weeks become firefighting weeks.

The new schedule, explained

The new model is designed to be predictable. The alpha phase runs for about six months, followed by a stabilization period. The first major release under the new model, Node 27.0.0, is set to arrive in April 2027. It enters LTS in October 2027 and reaches end of life around April 2030, giving it roughly 30 months of LTS support.

Compare that with the old system, where odd-numbered releases were Current and only even-numbered releases became LTS, and the improvement is obvious. Enterprises no longer have to explain to procurement why they are skipping every other major version. There is one release a year, it becomes LTS, and it is supported for about two and a half years. Planning gets simpler, and the endless Current versus LTS debate goes away.

Early adopters still get their channel. The alpha exists precisely so that people who want the newest V8, the newest crypto, and the newest features can test them months before stable. The difference is that the alpha is no longer a separate track that might never become LTS. It is the first stage of the one track that everyone will eventually run.

What teams should do now

If you maintain a library, install the alpha in CI alongside your current Node versions and watch for failures, especially around crypto and native modules. File issues early, while maintainers still have room to adjust. If you run production services, do not deploy the alpha. That should go without saying, but every major alpha tempts someone, and the breaking changes here are real.

If you are planning upgrades for 2027, pencil in Node 27's April stable release and October LTS date. Teams on Node 24 or earlier should think about whether to jump to Node 27 LTS in October or wait for the first LTS patch releases. The annual cadence makes that decision easier to schedule: one upgrade window a year, tied to a known calendar, rather than a rolling judgment call about which line to follow.

The tooling world around Node is moving at a similar pace. SvelteKit 3 moved configuration into vite.config.ts, a change that sounded small and mattered a lot, and OpenCode 2.0 rebuilt the open coding agent around a background service. Node's annual model is part of the same story: tools maturing from rapid, chaotic releases into predictable platforms that teams can plan around.

The bottom line

Node.js 27 alpha is not a release to install on Friday and forget. It is a signal about how Node will ship for the rest of the decade: one major a year, every line LTS, six months of alpha to catch the breaks. For library authors, the homework starts now. For everyone else, the payoff arrives in April 2027, when the stable release lands on a schedule you can actually put in a planning document.