Angular drops its six-month major cadence for one release a year

Angular's versioning-and-releases reference now describes a different cadence: a major release every 12 months, 4 to 6 minor releases for each major, and a patch or pre-release build almost every week. The page carries an explicit note that until v22, Angular ran a six-month major cycle with 1 to 3 minors per major. The revised text is live on angular.dev and in the framework's own docs on main.

The published schedule makes the shape concrete. v22 shipped on June 3, 2026. Everything scheduled after it for the next year is a minor — v22.1 the week of July 27, then v22.2 around September, v22.3 in November, v22.4 in January 2027, v22.5 in March. v23.0 is targeted for around June 2027, twelve months after v22 rather than six.

The support math is unchanged, which is the part to check before reading this as a support cut. Every major still gets 24 months: 12 active, then 12 of LTS carrying only critical fixes and security patches. v22's active phase ends in June 2027 and its LTS in June 2028; v21, released November 19, 2025, is in LTS until June 2027; v20, released May 28, 2025, runs to November 28, 2026. What the change actually alters is how many majors are alive at once. A fixed 24-month window over an annual cadence supports roughly two majors at a time instead of four, and a team that upgrades one major at a time now does that work once a year rather than twice.

The stated reasoning comes from the docs change, PR #69817, opened July 16, 2026: long-standing community requests for less frequent breaking changes, the upgrade cost carried by enterprise users, and a newer argument — that a longer cycle "provides increased API stability for developers using agentic workflows." Feature delivery is explicitly not being slowed. Features continue to ship in minors and only breaking changes are restricted to majors, which is why the minor allowance moved from 1–3 up to 4–6 in the same edit.

Reaction on the PR is mixed rather than celebratory: 21 thumbs-up against 8 thumbs-down and six "confused" reactions on the proposal itself, and the longest reply argues that recent major upgrades were already painless thanks to migration schematics and the deprecation policy, then asks the question the announcement leaves open — whether a slower major cadence should be read as a signal about the level of investment in Angular, or purely as reduced ecosystem churn. Angular has not answered that publicly. I track Angular's release history and its live support windows on the Angular versions page.