🅰️ Angular Versions and Support
Angular ships on a predictable schedule, and knowing that schedule is the difference between a routine upgrade and an emergency one. This page covers what is supported today, what changed at each major, and how to plan an upgrade.
Version-sensitive facts here were checked against Angular’s own release documentation. Re-check before acting on a support date.
Current support matrix
Section titled “Current support matrix”Angular publishes an explicit support window per major. As of Angular 22:
| Version | Status | Released | Active support ends | LTS ends |
|---|---|---|---|---|
| 22.x | Active | 2026-06-03 | 2027-06 | 2028-06 |
| 21.x | LTS | 2025-11-19 | 2026-06-03 | 2027-06 |
| 20.x | LTS | 2025-05-28 | 2025-11-19 | 2026-11-28 |
Anything older than 20 is out of support — no patches, no security fixes.
The cadence changed — check your assumptions
Section titled “The cadence changed — check your assumptions”Angular historically shipped a major every 6 months with an 18-month support window. Since v22 the cadence is a major every 12 months, with 24 months of total support:
- Active phase (12 months) — regular updates and patches.
- LTS phase (12 months) — critical fixes and security patches only.
Plus roughly 4–6 minors per major and weekly-ish patches.
This matters for planning: upgrade budgeting built on the old 6-month rhythm will over-estimate how often you must move, and support-window maths built on 18 months will under-estimate how long you have.
What changed, by major
Section titled “What changed, by major”Only the shifts that change how you write Angular. Older entries are compressed deliberately — they are history, not guidance.
| Version | Year | The shift that mattered |
|---|---|---|
| AngularJS (1.x) | 2010 | The original framework. A different product — see AngularJS |
| Angular 2 | 2016 | Full rewrite: components, TypeScript, DI |
| Angular 9 | 2020 | Ivy became the default compiler/renderer |
| Angular 14 | 2022 | Standalone components (preview) and typed reactive forms |
| Angular 15 | 2022 | Standalone APIs stable |
| Angular 16 | 2023 | Signals introduced (developer preview) |
| Angular 17 | 2023 | Built-in control flow (@if/@for/@switch), @defer, new docs site |
| Angular 18 | 2024 | Zoneless change detection (experimental) |
| Angular 19 | 2024 | Standalone by default; incremental hydration; details |
| Angular 20 | 2025 | Signals ecosystem matured; details |
| Angular 21 | 2025 | Zoneless is the default; Signal Forms arrive |
| Angular 22 | 2026 | Signal Forms graduate to public API; Angular Aria; 12-month cadence begins |
The three that reshaped how Angular is written
Section titled “The three that reshaped how Angular is written”Standalone components (14–19). NgModules stopped being the unit of composition. By 19 standalone is the default for new code, and NgModule is legacy-and-interop surface rather than the way you structure an app.
Signals (16–21). A reactive primitive that the framework itself understands, which made the next change possible.
Zoneless (18–21). Because signals tell Angular precisely what changed, Angular no longer needs to monkey-patch every async browser API to guess. Zoneless is the default from v21. If you are on 21+ and still shipping zone.js, something is explicitly opting you back in.
See Change Detection and Zoneless Angular for what that means in practice.
Which version should you target?
Section titled “Which version should you target?”| Situation | Target |
|---|---|
| New application | 22 — current, longest runway |
| Actively developed app on 20/21 | Move to 22 while both are still supported |
| App on 19 or older | Out of support. Plan an upgrade now — see below |
| Constrained by a third-party library | Upgrade to the newest major that library supports, then push the library |
The trap to avoid: falling more than two majors behind. Angular’s upgrade tooling assumes you move one major at a time, and each hop you skip compounds the breaking changes you must reason about simultaneously.
Upgrading
Section titled “Upgrading”Angular’s upgrade story is unusually good, and most of it is automated:
# Check what applies to you — the interactive guide is the canonical source# https://angular.dev/update-guide
# Upgrade one major at a time, never twong update @angular/core@21 @angular/cli@21ng update @angular/core@22 @angular/cli@22ng update runs schematics — codemods that rewrite your source for known breaking changes, rather than just bumping a version number. There are dedicated migrations for the big shifts:
ng generate @angular/core:control-flow # *ngIf/*ngFor → @if/@forng generate @angular/core:standalone # NgModules → standaloneng generate @angular/core:signal-input-migration # @Input() → input()ng generate @angular/core:signal-queries-migration # @ViewChild() → viewChild()ng generate @angular/core:output-migration # @Output() → output()ng generate @angular/core:inject # constructor DI → inject()Run them one at a time, commit between each, and let your test suite gate the change. A migration that produces a 4,000-line diff is not reviewable as one commit.
The full treatment — compatibility matrices, diagnosing third-party blockers, incremental vs rewrite, rollback strategy — is in Angular Modernization and Version Upgrades.
AngularJS
Section titled “AngularJS”AngularJS is the name for every 1.x release of the original JavaScript framework (first released in 2010). It is a different product from Angular 2 and later: it uses controllers, $scope and two-way digest-cycle binding instead of TypeScript components, and there is no in-place upgrade from one to the other. Google ended Long Term Support for AngularJS on December 31, 2021, so it receives no further fixes, including security fixes.
You will still meet AngularJS in older line-of-business apps. Its entry point is the ng-app directive, which marks the root element and auto-bootstraps the application; only one app per HTML document can be auto-bootstrapped this way, and any others must be started with angular.bootstrap(). The following fragment (not run here) shows the classic pattern of a module, a controller and ng-model binding:
<div ng-app="ordersPortal" ng-controller="CustomerCtrl"> First name: <input type="text" ng-model="firstName"> Last name: <input type="text" ng-model="lastName"> <p>Ship to: {{ firstName + ' ' + lastName }}</p></div><script> angular.module('ordersPortal', []).controller('CustomerCtrl', function ($scope) { $scope.firstName = 'Avery'; $scope.lastName = 'Stone'; });</script>If you maintain such an app, plan a migration rather than an upgrade: the options are an incremental hybrid using @angular/upgrade (running AngularJS and Angular side by side and moving screens one at a time) or a rewrite, and either way the unsupported runtime is a security liability. See Modernization and version upgrades for planning.
Common mistakes
Section titled “Common mistakes”- Skipping majors to “catch up faster”. It is slower, because schematics only handle one hop.
- Upgrading Angular while a peer dependency is unsupported. Check RxJS, TypeScript, Node, and your component library first — they are the usual blocker.
- Treating LTS as indefinite. LTS is 12 months and receives security fixes only; it is a runway, not a resting place.
- Assuming a 6-month cadence. That changed at v22.
- Running every migration in one commit, producing a diff nobody can review and a bisect nobody can use.
Related pages
Section titled “Related pages”- Angular 19 Features · Angular 20 Features
- Change Detection and Zoneless Angular
- Angular Modernization and Version Upgrades