Node.js 26, which shipped in April, is the last version under the old two-majors-per-year model. From Node.js 27 onward — targeting October 2026 — the project ships one major in April, promotes it to LTS in October, and retires the odd/even distinction that has long tripped up developers tracking support timelines. This is a meaningful governance shift, not just a calendar tweak. Collapsing the cadence means every major is an LTS candidate, which simplifies upgrade planning and reduces the churn of maintaining odd-numbered releases that never reach LTS. The practical question is whether a single annual release window creates enough pressure around breaking-change batching.