Node.js shifts to annual major updates
Node.js is changing its release cadence to a single major update per year, potentially simplifying upgrade planning for agencies.
The move to a single major release per year, starting with version 27.x, aims to simplify the upgrade process, as every release will now be a Long-Term Support (LTS) version. This eliminates the confusion of odd/even release distinctions, where odd-numbered releases had minimal adoption and even-numbered releases were designated LTS. The previous release schedule, established a decade ago during the io.js merger, no longer reflects actual usage patterns. Most users waited for LTS versions anyway, so this change aligns with how organizations typically adopt Node.js. The new schedule offers predictability for teams planning upgrades and allocating resources. This shift also addresses the sustainability of the project, which is primarily maintained by volunteers. Managing security releases across multiple active release lines has become difficult. Reducing the number of concurrent release lines allows maintainers to focus on better supporting the releases that are widely used. Library authors are encouraged to integrate Alpha releases into their CI pipelines early to report bugs before they impact users. An alpha channel will be available for early testing with semver-major changes, using a semver prerelease format (e.g., 27.0.0-alpha.1). Version numbers will align with the calendar year of the initial current release (e.g., 27.0.0 in 2027).
