Node.js Cuts Release Cycle

The previous six-month cycle, with alternating Long-Term Support (LTS) and 'Current' releases, was in place for nearly a decade. This model meant even-numbered versions (like v22, v24) received long-term support, while odd-numbered versions had a short, eight-month lifespan. This rapid, dual-track system was a response to the Node.js-io.js fork in 2014-2015, designed to accelerate feature integration from Google's V8 engine and establish a predictable release schedule. However, the constant cycle of new releases led to significant "upgrade fatigue" among developers and placed a heavy burden on the project's volunteer maintainers. The proposal to switch to a single annual release was championed by members of the Node.js Technical Steering Committee (TSC) and the Release Working Group. Key figures in Node.js governance, such as Rafael Gonzaga and Matteo Collina, have been instrumental in shaping the platform's direction and release strategies. Under the new model, every major version will become an LTS release, eliminating the confusing distinction between odd and even-numbered versions. This change also shortens the total LTS duration from 30 months to a more streamlined 24 months, consisting of 12 months in 'Active LTS' and 12 months in 'Maintenance'. This annual cadence aligns Node.js more closely with other major enterprise technologies. For comparison, .NET also has an annual release schedule, with LTS versions supported for three years. Java has shifted to a two-year cycle for LTS releases, and Python has adopted a 12-month cadence. The goal is to provide a more predictable and stable roadmap for large-scale enterprise users, who often plan upgrades on a 12 to 24-month cycle. By ensuring every major release is supported for two years, the Node.js team aims to simplify long-term planning and reduce the maintenance overhead for both the project and its extensive user base.