Release

This repository tracks the release schedule and processes for Node.js, the popular tool for running JavaScript on servers and other environments outside a browser. There is very little code here. The primary content is documentation about when each version of Node.js is released, how long it is supported, and who is responsible for making releases happen.

Node.js follows a predictable release pattern. New major versions come out every six months, in April and October. Even-numbered versions, such as 22, 24, and 26, become Long Term Support releases, meaning they receive updates and security fixes for several years. Odd-numbered versions receive a shorter support window and are not promoted to Long Term Support status. The README includes a full table showing the current status of every version ever released, from the very first to the most recent.

There are three active phases a release can be in. Current means it is receiving the latest non-breaking changes. Active LTS means it is stable and receiving reviewed bug fixes and updates. Maintenance means it only gets critical security fixes. Eventually each version reaches end of life and receives no further updates.

The working group that manages all of this is divided into three teams. The Releasers team handles the technical work of building and signing each release. The Backporters team picks fixes from newer versions and applies them to older supported versions. The CITGM team runs a suite of tests against popular packages to confirm that a release does not break widely used software.

This repository is essentially a governance and scheduling document for the people who maintain Node.js releases, along with a public record of the release timeline for anyone who needs to know when a version they depend on will stop receiving support.