If you still have an Angular 20 app in production, mark 28 November 2026 in your calendar. According to Angular’s official release and support policy, that is the day long-term support for Angular 20 ends. After it, the Angular team stops shipping 20.x patches, including security fixes.

The good news: the current version, Angular 22, is in active support, and Angular 22.3.0 shipped on 18 November 2026. This guide shows you how to check where you are, what you need before upgrading, and how to move from 20 to 22 one major version at a time with ng update.

Angular’s support windows

Angular supports each major version for 24 months in total: 12 months of active support with regular updates, followed by 12 months of LTS, where only critical fixes and security patches are released. Here is the current table from angular.dev:

Version Status Released Active ends LTS ends
^22.0.0 Active 2026-06-03 2027-06 2028-06
^21.0.0 LTS 2025-11-19 2026-06-03 2027-06
^20.0.0 LTS 2025-05-28 2025-11-19 2026-11-28

Versions 2 to 19 are already unsupported. In LTS, a fix is only considered if it addresses a newly found security vulnerability or a regression caused by a third-party change, such as a new browser version.

So you have two choices:

  • Go to Angular 21 to get supported again quickly. It’s in LTS until June 2027.
  • Go all the way to Angular 22, which is in active support until June 2027 and LTS until June 2028. This is the better long-term move.

Step 1: Check what you’re running

From the project root:

npx ng version
node --version
npx tsc --version

Write down the Angular, Node.js and TypeScript versions. You’ll need them in the next step.

Step 2: Check Node.js and TypeScript requirements

Each Angular major supports specific Node.js and TypeScript ranges. From the official version compatibility table:

Angular Node.js TypeScript RxJS
22.x ^22.22.3, ^24.15.0 or ^26.0.0 >=6.0.0 <6.1.0 ^6.5.3 or ^7.4.0
21.x ^20.19.0, ^22.12.0 or ^24.0.0 >=5.9.0 <6.0.0 ^6.5.3 or ^7.4.0
20.2.x / 20.3.x ^20.19.0, ^22.12.0 or ^24.0.0 >=5.8.0 <6.0.0 ^6.5.3 or ^7.4.0

Two things stand out:

  1. Angular 22 drops Node.js 20. If your CI or Docker images still use Node 20, move to Node 22 (at least 22.22.3), 24 (at least 24.15.0) or 26 before the Angular 22 step. Node 22 and 24 also work for Angular 21, so you can switch Node first and keep everything else the same.
  2. Angular 22 needs TypeScript 6.0.x. Not 5.9, and not 7. ng update normally handles the TypeScript bump for you, but check any other tool in your repo that pins TypeScript.

Pin the Node version in one place so local machines and CI match:

echo "24" > .nvmrc
nvm install && nvm use

Step 3: Prepare the project

Before running any update:

git checkout -b upgrade-angular-22
git status            # working tree should be clean
npm ci
npx ng test --watch=false
npx ng build

A clean branch and a passing baseline make it easy to see which failures the upgrade caused.

Also make a list of third-party Angular libraries in package.json (UI kits, state management, charting, auth). Check that each one has a release supporting Angular 21 and 22. This is usually what holds upgrades back.

Step 4: Update from 20 to 21

Angular’s update tooling is designed to go one major version at a time. Don’t jump from 20 straight to 22.

npx ng update @angular/core@21 @angular/cli@21

ng update updates the packages and runs migration schematics that rewrite code where APIs changed. Read the output carefully; it lists every migration it ran and anything it couldn’t change automatically.

If you use Angular Material and the CDK, update them in the same step:

npx ng update @angular/material@21

Then verify:

npx ng build
npx ng test --watch=false

Commit this as its own step:

git add -A
git commit -m "Upgrade to Angular 21"

For version-specific manual steps, use the interactive Angular update guide. Choose “20.0” to “21.0” and your app’s complexity, and it lists what to check.

Step 5: Update from 21 to 22

Make sure Node.js meets the Angular 22 range first, then:

npx ng update @angular/core@22 @angular/cli@22
npx ng update @angular/material@22   # if you use it

Check that TypeScript ended up in the 6.0 range:

npx tsc --version
npm ls typescript

If npm ls shows another package pulling in a different TypeScript version, update or remove that package.

Build, test and commit again:

npx ng build
npx ng test --watch=false
git commit -am "Upgrade to Angular 22"

Step 6: Get on the latest 22.x patch

After the major upgrade, move to the latest minor and patch. At the time of writing that’s 22.3.0:

npx ng update @angular/core @angular/cli
npx ng version

Running ng update without a version moves you to the latest published release (22.3.0 right now). The 22.3.0 release is mostly compiler work. Among other things, the compiler now reports unknown property bindings on explicit ng-template elements, and disallows attribute and property names that start with a colon. So it may surface template mistakes that previously went unnoticed. Fix those rather than suppressing them.

Common problems and fixes

“Package X has an incompatible peer dependency”
A third-party library hasn’t declared support for the new Angular version yet. Check for a newer release first. As a last resort you can run ng update with --force, but only if you’ve confirmed the library actually works. A forced install that hides a real incompatibility will break at runtime.

Build fails on Node.js version
The Angular CLI checks the Node.js version and complains about unsupported ones. Upgrade Node in your local environment, CI image and Dockerfile, for example:

FROM node:24-slim AS build

Type errors after the TypeScript bump
Newer TypeScript versions are often stricter. Fix the errors in place, and commit the fixes separately from the version bump so code review stays readable.

Tests pass locally but fail in CI
This usually means CI still has the old Node.js version or a cached node_modules. Clear the cache and confirm the Node version in the CI logs.

A quick upgrade checklist

  1. ng version: note Angular, Node and TypeScript versions.
  2. Move Node.js to 22.22.3+, 24.15.0+ or 26.
  3. Check that third-party libraries support Angular 21 and 22.
  4. ng update @angular/core@21 @angular/cli@21, then build, test and commit.
  5. ng update @angular/core@22 @angular/cli@22, then build, test and commit.
  6. Update to the latest 22.x patch.
  7. Deploy before 28 November if you can, or as soon as possible after.

Takeaway

Angular 20 stops getting security fixes on 28 November 2026. The safest path is to upgrade one major at a time: fix your Node.js version first, run ng update to 21, then to 22, and commit after each step. Once you’re on Angular 22 you’re covered by active support until June 2027 and LTS until June 2028, and future upgrades will be much smaller if you keep up with each new major.