Node.js Release Schedule Explained: Current, Active LTS, Maintenance and the Change in Node.js 27

The short answer

Run an LTS line in production. Today that means Node.js 24, in Active LTS until 20 October 2026 and supported until 30 April 2028, or Node.js 22, already in Maintenance and supported until 30 April 2027. Node.js 26 becomes LTS on 28 October 2026 and is supported until 30 April 2029. Node.js 20 reached end of life on 30 April 2026. From Node.js 27, the project ships one major release a year instead of two, every major becomes LTS, and a new Alpha channel replaces the odd-numbered releases for early testing.

The three phases: Current, Active LTS and Maintenance

The Node.js Release Working Group defines three phases for a release line:

• Current: the first six months. The line picks up most non-breaking changes that land on the main branch. It is for early adopters and library authors adding support for the new major.
• Active LTS: twelve months in which the line gets new features, bug fixes and updates that the Release team has audited as appropriate and stable.
• Maintenance: eighteen months of critical bug fixes and security updates only. New features land rarely, usually to ease migration to a later line.

Add the phases up and an LTS line is supported for about three years from its first release, of which 30 months are LTS. Under the model that applies up to Node.js 26, odd-numbered majors never become LTS: they are Current for six months, get a short maintenance tail, and reach end of life about eight months after release. Node.js 25, for example, ended on 1 June 2026.

Node.js release dates: 20, 22, 24 and 26

The dates come from the schedule file in the nodejs/Release repository, which the project describes as subject to change. The Release Working Group commits to choosing each transition date no later than the first day of the month in which it happens.

What changes with Node.js 27

On 10 March 2026 the Node.js releasers announced that, starting with 27.x, Node.js moves from two major releases a year to one. The new model works like this:

• One major a year, released in April and promoted to LTS in October.
• Every release becomes LTS. The odd and even distinction goes away.
• Version numbers follow the calendar: 27.0.0 in 2027, 28.0.0 in 2028.
• A new Alpha channel runs for six months, from October to March, before each release. Alpha builds may contain breaking changes, are signed and tested, and are meant for library authors and CI pipelines. The project says plainly that they are not intended for production use.
• The support window stays about the same: six months Current and 30 months LTS, 36 months from first release to end of life.

The project gave three reasons: odd-numbered releases saw little adoption, the odd and even split confused newcomers, and maintaining security releases across four or five active lines had become hard for a mostly volunteer team to sustain. Node.js 26 is the last line under the old model. The release schedule lists Node.js 27 with an Alpha from 28 October 2026, a first release on 22 April 2027, and end of life on 30 April 2030.

Which Node.js version should you run?

• New services: Node.js 24 today, or 26 once it becomes LTS on 28 October 2026 if your dependencies support it. 26 gives a year more runway, to 30 April 2029.
• Services on Node.js 22: you are in Maintenance, with security fixes until 30 April 2027. Plan the move to 24 or 26 now rather than in the spring.
• Services on Node.js 20 or older: you have no upstream security fixes. Upgrade, or cover the runtime while you do. Our Node.js 18 and 20 to 22 and 24 upgrade guide walks through the breaking changes.
• Library authors: from October 2026, add the Node.js 27 Alpha to CI. The project specifically asks for it, so bugs surface before they reach users on LTS.

Two habits help regardless of version. Pin the major in your Dockerfiles and CI images so a base image update cannot move you to a new line by accident. And track the Maintenance start date as well as end of life, because that is when non-security fixes stop.

Where OSSeva fits

OSSeva for Node.js ships CVE-patched runtimes for Node.js 14, 16, 18 and 20 after community end of life, and covers 22 in Maintenance LTS, so an upgrade can follow your release calendar instead of the project's. OSSeva Assure adds transitive npm dependency scanning, an HTTP/2 and TLS review and version upgrade planning; OSSeva Operate adds 24/7 process and cluster health monitoring, a 15-minute P1 response, PM2 and cluster mode support and execution of the major version migration. Node.js is priced per application runtime, not per core or deployment instance, and sits under one contract with the rest of your stack. See the Node.js end-of-life dates, Node.js 22 end of life, Node.js vulnerabilities by version and Node.js end-of-life support providers, or book a discovery call for a quote.

Frequently asked questions

What is the difference between Active LTS and Maintenance LTS?

Active LTS lasts twelve months and gets audited new features, bug fixes and updates. Maintenance lasts eighteen months and gets only critical bug fixes and security updates. Both are supported for production use.

Is Node.js 24 LTS?

Yes. Node.js 24, codenamed Krypton, entered Active LTS on 28 October 2025, moves to Maintenance on 20 October 2026 and reaches end of life on 30 April 2028.

When does Node.js 22 reach end of life?

On 30 April 2027. It has been in Maintenance since 21 October 2025, so it now gets only critical and security fixes.

Why are odd-numbered Node.js versions not LTS?

Up to Node.js 26, a new major shipped every six months and only the even-numbered April release was promoted to LTS. Odd-numbered October releases were short-lived. From Node.js 27 that distinction ends: one major a year, and every one becomes LTS.

Should I use the Current release in production?

Generally no. The project's guidance is that production applications should use Active LTS or Maintenance LTS releases. Current is for testing and for library authors.

What is the Node.js Alpha channel?

A six-month pre-release channel, starting in October 2026 for Node.js 27, in which breaking changes can still land. It is for library authors and CI, not for production.