Node.js drops to one major release a year to cut the branches its maintainers patch

Under the old schedule, a new Current line shipped every April and October. The even-numbered one was promoted to LTS for 30 months. The odd-numbered one lasted about six months and was dropped ^[6]. According to the Release Working Group's announcement, as quoted by dev.to, the pattern came out of the io.js merger "as an educated guess of what enterprises would need" ^[7].

Production teams answered the guess by skipping half of it. The working group's usage data shows odd releases saw minimal real-world adoption, and most teams waited for LTS ^[8]. The odd branch still needed security backports for the six months it lived ^[9]. Add the overlapping LTS lines and the total is the "four or five active lines" the team cites as its burden ^[9].

The new lifecycle is easy to count. Node.js 27 reaches its first stable release in April 2027 and end of life in April 2030 ^[3], so each line is in support for 36 months after it ships ^[1]. One major a year at 36 months each gives three released lines in support at any time once the old-schedule lines age out, plus an Alpha from October to March ^[2]. The dev.to post puts the overlap at two to three LTS branches, the same as before, and calls the efficiency gain modest ^[12]. I think that is right. Labelling every release LTS is easy when there is one release a year ^[5]. The LTS overlap did not move. The saving is one short-lived branch a year that almost nobody deployed ^[2][8].

The burnout account is the post's own characterisation. It says the release team was burning out trying to patch security holes across four or five live branches ^[13]. The working group passages it quotes are about adoption and line count ^[7][8][9]. That evidence supports the narrower claim that the change cuts the number of branches carrying security backports ^[2].

For LTS-only shops, the working group wrote: "If you already only upgrade to LTS versions, little changes beyond version numbering. LTS support windows remain similar, and now every release becomes LTS." ^[10]

The cost moves to teams that took new APIs from the Current line. They now wait roughly a year between majors instead of six months ^[11]. The working group's data on odd-release adoption suggests those teams are few ^[8]. Their nearest substitute is the Alpha phase. It runs October to March and is the stage for early testing and breaking changes ^[4]. For a team that ran production code on odd releases, the terms of Alpha decide whether the loss is six months of lead time or a change of channel. The post does not say how Alpha builds are distributed or what stability they promise.