Angular version support and end of life

Angular 22 is the current major. Angular 21 and 20 still receive security fixes, and Angular 20 leaves support in November 2026. Every version from v19 down is unsupported.

How the release cadence works

Angular uses semantic versioning: major.minor.patch. Breaking changes only arrive in major releases, and every major goes through two support stages.

• Active support. Regularly scheduled updates and patches.
• Long-term support (LTS). Only critical fixes and security patches.

Until Angular 21 the team shipped a major about every six months. Each major had 6 months of active support followed by 12 months of LTS, about 18 months in total.

Starting with Angular 22, the official release page describes a different rhythm: one major release every 12 months, with 4 to 6 minor releases in between. The support window is now typically 24 months, split into 12 months of active support and 12 months of LTS. The published schedule places Angular 23 around June 2027. The Angular team presents these dates as general guidance that can change.

What gets fixed during LTS

During LTS a fix is considered in two cases only: a newly identified security vulnerability, or a regression caused by a third-party change such as a new browser version. New features and ordinary bug fixes do not reach LTS versions.

Angular versions from v9 to v22

Status as of October 2, 2026. Dates are given by month. For exact days, check the official release page at angular.dev/reference/releases.

What "unsupported" means

An unsupported version keeps running. What stops is everything around it:

• No security patches. Vulnerabilities found after the end of LTS are fixed only in supported versions.
• No fixes for browser regressions. If a new browser release breaks something, the fix lands in supported versions only.
• Frozen tooling. Each major is tied to a range of Node.js and TypeScript versions. The official compatibility table describes the data for old versions as correct when the version left LTS and provided without further guarantees.
• Libraries move on. Angular Material, NgRx and most third-party libraries publish releases for current majors.
• Audit findings. Security reviews flag frameworks that no longer receive patches.

Third-party vendors sell extended support for unsupported Angular versions. It can cover a compliance gap while you upgrade. It does not bring the app closer to a current version.

How deprecations add up

When the Angular team deprecates an API, the current policy keeps it available for at least one more major release, which is roughly one year under the yearly cadence. Removals only happen in major releases. An app that skips several majors meets all those removals together, which is the main reason old upgrades feel large.

How to plan upgrades

• Know your date. Find your major in the table and note when its LTS ends or ended.
• Budget one major per year. With the yearly cadence that started with v22, one upgrade a year keeps the app inside the support window.
• Move one major at a time. The official update policy covers ng update from one major to the next. An app several majors behind repeats that step. The details are in Angular upgrade strategy for old versions.
• Check the dependencies first. Node.js, TypeScript, RxJS, Angular Material and NgRx decide how fast you can go.
• Keep AngularJS separate. AngularJS (1.x) is a different framework with a different path. See AngularJS migration and Rewrite, hybrid or micro-frontends.

More in this section

• Angular 9: end of life and how to upgrade
• Angular 10: end of life and how to upgrade
• Angular 11: end of life and how to upgrade
• Angular 12: end of life and how to upgrade