Upgrades and deprecations
Upgrade Angular 15 to Latest: Seven ng update Runs, One Major at a Time
In short
To upgrade Angular 15 to latest, plan seven separate `ng update` runs, because the official policy only updates across one major at a time. Today that ends at 22.3.0. Angular 15 has had no fixes for a long time, and v20, a tempting stopping point, leaves LTS on 28 November 2026. Node changes once on the way; TypeScript changes at every hop.
Why can't ng update go from 15 to 22 in one step?
The versioning page sets two conditions for ng update. The target must be a supported version, and the version you start from must be within one major of it. For a longer jump the page says to perform each update one major version at a time.
From 15 that means 16, 17, 18, 19, 20, 21 and finally 22: seven runs, each with its own migrations. Skipping one also skips the code transformations written for that major, which is where most of the automated help lives.
There is a second reason the order matters. Versions 16 to 19 are no longer supported, so you cannot settle on any of them. They are rungs on a ladder, useful only long enough to run their migrations and pass your tests.
Checked against: source 1
Which Angular versions are supported on 20 November 2026?
The release page lists three lines under support and states that v2 to v19 are no longer supported. The npm registry tags 22.3.0 as latest, which matches the schedule's v22.3 entry for around November 2026.
The policy itself changed this year. Until v22 a new major came every six months; from v22 the page expects one major every 12 months, with four to six minors each. Every major is typically supported for 24 months: 12 active, then 12 of LTS that only receives critical fixes and security patches.
| Line | Released | Status | Active ends | LTS ends |
|---|---|---|---|---|
| 22 | 3 Jun 2026 | Active | Jun 2027 | Jun 2028 |
| 21 | 19 Nov 2025 | LTS | 3 Jun 2026 | Jun 2027 |
| 20 | 28 May 2025 | LTS | 19 Nov 2025 | 28 Nov 2026 |
| 15 to 19 | 2022 to 2024 | Unsupported | Ended | Ended |
What Node.js and TypeScript does each hop need?
The compatibility table gives a Node range and a TypeScript range for every minor. The rows below use the .0 release of each major, since that is the version the hop lands on. TypeScript has to move at every single step; Node does not.
| Hop to | Node.js accepted | TypeScript accepted |
|---|---|---|
| 16.0 | ^16.14.0 or ^18.10.0 | >=4.9.3 <5.1.0 |
| 17.0 | ^18.13.0 or ^20.9.0 | >=5.2.0 <5.3.0 |
| 18.0 | ^18.19.1, ^20.11.1 or ^22.0.0 | >=5.4.0 <5.5.0 |
| 19.0 | ^18.19.1, ^20.11.1 or ^22.0.0 | >=5.5.0 <5.7.0 |
| 20.0 | ^20.19.0, ^22.12.0 or ^24.0.0 | >=5.8.0 <5.9.0 |
| 21.x | ^20.19.0, ^22.12.0 or ^24.0.0 | >=5.9.0 <6.0.0 |
| 22.x | ^22.22.3, ^24.15.0 or ^26.0.0 | >=6.0.0 <6.1.0 |
Checked against: source 2
How do you upgrade Angular 15 to latest with only one Node switch?
Read the Node column as overlapping windows. A Node 18 release at 18.19.1 or later satisfies Angular 15 (which accepts ^18.10.0) and every hop up to 19. A Node 22 release at 22.22.3 or later satisfies 18, 19, 20, 21 and 22. So the joined plan is to run 15 to 17 on Node 18, switch to Node 22 once you sit on 18 or 19, and keep it to the end.
One wrinkle deserves a check. The update guide's v20 step says Node 20.11.1 or later, while the compatibility table asks for ^20.19.0 or ^22.12.0. The table is the stricter of the two, so I would plan against it.
Node 18 itself is past its end of life, as the Node 18 upgrade route shows, so keep that stage short: it is a build environment for three hops, not a place to deploy from.
What does ng update do for you, and what is left over?
The command reference describes it as updating packages and running their migrations. ng update @angular/core@16 @angular/cli@16 is the form the guide gives for the first hop, and Angular Material needs its own ng update @angular/material@16. The --create-commits flag commits each update and migration, which makes a failed hop easy to inspect. Modified or untracked files block the run unless you pass --allow-dirty, which is off by default.
--force ignores peer dependency mismatches. It does not make a third-party library compatible, so a library pinned to an older Angular still has to be upgraded or replaced; this fix page covers the error you see in that case.
What the command does not do is the manual part of the Update Guide. That guide builds a checklist for a from-version, a to-version and an app complexity level (basic, medium or advanced). A few entries say the CLI or an automated migration makes the change for you. Many others describe new behaviour in tests, router timing or server rendering, which no migration can judge on your behalf.
Which removals are most likely to stop the build on the way?
These come only from the Update Guide's entries for each target version. They are the items I would search the codebase for before starting each hop.
- To 16: ngcc is gone, so View Engine libraries no longer work.
entryComponents,ReflectiveInjectorandrenderModuleFactorywere removed. - To 17: legacy Material components deprecated in 15 are removed, so the guide says to run
ng generate @angular/material:mdc-migrationfirst.NgSwitchnow compares with===, and Zone.js deep imports must change. - To 18:
asyncfrom@angular/corebecomeswaitForAsync, and the WebWorker platform helpers are gone. - To 19: components, directives and pipes are standalone by default; declarations that live in an NgModule need
standalone: false, which the CLI adds. - To 20:
TestBed.get()and theInjectFlagsenum are removed, andafterRenderis renamedafterEveryRender. - To 21: zone-based apps need
provideZoneChangeDetection()(an automated migration should add it), andUpgradeAdapterandNgModuleFactoryare removed. - To 22: components without a
changeDetectionsetting default to OnPush, andng updatepins existing ones toChangeDetectionStrategy.Eager.strictTemplatesdefaults to true, andComponentFactoryResolver,provideRoutes()and the Hammer.js integration are removed.
Checked against: source 3
What else do people ask?
Can a project stop at Angular 20 for now?
Only for a few days. The release page gives v20 an LTS end of 28 November 2026. v21 is covered until June 2027 and v22 until June 2028, so 22 is the only target with a full year of active support left.
Does the Update Guide replace reading the changelog?
No. The versioning page says deprecations are announced in the changelog, and the guide is a curated subset. It is the right checklist for each hop, while the changelog is where an unexplained failure is traced.
Sources
- angular.dev, Angular versioning and releases (support window, release schedule, update paths), fetched 2026-11-20
- angular.dev, Version compatibility (Node.js, TypeScript, RxJS per version), fetched 2026-11-20
- angular.dev Update Guide and its recommendations data in the angular/angular repository, fetched 2026-11-20
- angular.dev CLI reference, ng update, fetched 2026-11-20
- angular.dev, Keeping your Angular projects up-to-date, fetched 2026-11-20
- npm registry, @angular/core dist-tags and release dates, fetched 2026-11-20
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. This page joins angular.dev documents and the npm registry, fetched on 20 Nov 2026 (the release and support policy, the version compatibility table, the Update Guide's data and the ng update reference). I did not upgrade an app for it. It does not cover Nx workspaces, third-party component libraries, AngularJS hybrids or custom builders. Found a mistake? Tell me.