Skip to content
ToolShedby Wasim Shaikh

Angular 20 End of Life on 28 November 2026: What to Do Now

Wasim · 14 Nov 2026

What Happens on 28 November 2026?

Angular 20 reaches end of life on 28 November 2026. That date comes straight from the official Angular release policy, where Angular 20 is listed with active support ending on 19 November 2025 and LTS ending on 2026-11-28.

After that date Angular 20 gets no more patches of any kind, including critical bug fixes and security fixes. Your app won't stop working on 29 November, but:

  • A newly found vulnerability in @angular/core, @angular/common or the router won't be fixed for v20.
  • Security scanners and audits (SOC 2, ISO 27001, PCI DSS, client pen tests) will start flagging an unsupported framework.
  • Libraries such as Angular Material, NgRx and component kits drop v20 from their newer releases, so you can't pick up their fixes either.

If you are on Angular 19 or older, you are already unsupported, and everything below applies to you too.


Which Angular Versions Are Still Supported?

Version Released Active support ends LTS ends Status in Nov 2026
Angular 22 3 Jun 2026 Jun 2027 Jun 2028 Active
Angular 21 19 Nov 2025 3 Jun 2026 Jun 2027 LTS
Angular 20 28 May 2025 19 Nov 2025 28 Nov 2026 LTS, ending
Angular 19 and older Unsupported

Angular now ships one major a year with 24 months of support, so there is no Angular 23 until about June 2027. I covered the new schedule in Angular Moves to Yearly Releases.


Step 1: Check Which Version You Are On

Run this in your project root:

ng version

Look at the Angular: line and at @angular/core in the package list. If it starts with 20., this article is for you. Also note your Node.js and TypeScript versions, because they decide how much prep work the upgrade needs.


Your Three Options

Angular 22 is supported until June 2028, the longest window available. You go through 21 on the way anyway, so stopping at 21 saves little and buys only seven months (its LTS ends in June 2027).

Option 2: Upgrade to Angular 21

This is a smaller jump: Angular 21 still accepts TypeScript 5.9 and Node 20.19+, while Angular 22 needs TypeScript 6.0 and Node 22.22.3+. Pick it only if your toolchain or a key library can't move to 22 yet, and plan the 21 → 22 step before June 2027.

Option 3: Stay on 20 with paid extended support

Third-party vendors such as HeroDevs sell security patches for end-of-life Angular versions. This makes sense for an app that is being retired or frozen for compliance reasons. For anything you still actively develop, it only postpones the upgrade and costs money every year.


Step 2: Upgrade Your Toolchain First

Check these before you run ng update, because they cause most failed upgrades:

Angular 20 Angular 21 Angular 22
Node.js 20.19+, 22.12+, 24 20.19+, 22.12+, 24 22.22.3+, 24.15+, 26
TypeScript 5.8–5.9 5.9 6.0

Node 20 is dropped in Angular 22, and early Node 22 and 24 releases are below the new minimum. Update Node on developer machines, CI runners and Docker images. The Angular Node.js & TypeScript Version Checker tells you whether a given combination works, and the official version compatibility table has the full list.


Step 3: Upgrade One Major at a Time

ng update moves one major version per run, so go 20 → 21 → 22. Start from a clean git branch and commit after each step.

# 20 -> 21
ng update @angular/core@21 @angular/cli@21
ng update @angular/material@21   # only if you use Material / CDK

# build and test, then commit

# 21 -> 22
ng update @angular/core@22 @angular/cli@22
ng update @angular/material@22

Update third-party Angular libraries (NgRx, ngx-translate, PrimeNG and so on) to versions that support each major as you go. The Angular Upgrade Planner: 20 to 22 gives you the full checklist for this exact path, and the official Angular Update Guide lists the same steps.


What Changes Between Angular 20 and 22

The ng update migrations handle most of this automatically, but these are the changes worth reviewing.

Angular 21

  • Zoneless is the default. The migration adds provideZoneChangeDetection() to existing apps, so nothing breaks. You can remove Zone.js later.
  • Vitest is the default test runner for new projects. Existing projects keep Karma, which is still supported.
  • Host bindings are type-checked, so invalid @HostBinding / @HostListener expressions become compile errors.
  • HttpClient is provided by default. Keep provideHttpClient() if you use interceptors or other features.

Angular 22

  • OnPush is the default change detection strategy, and the old Default strategy is renamed Eager. The migration adds changeDetection: ChangeDetectionStrategy.Eager to existing components so behavior stays the same.
  • HttpClient uses fetch instead of XMLHttpRequest. The migration adds withXhr() where you need upload progress events.
  • strictTemplates is on by default, so expect some new template type errors.
  • Template optional chaining returns undefined, not null, when the left side is null. Check code that compares with === null.
  • Route params and data are inherited from parent routes by default (paramsInheritanceStrategy: 'always').
  • Signal Forms, resource() / httpResource() and Angular Aria are stable, and there is a new @Service() decorator for root services.

After the Upgrade: Modernize at Your Own Pace

Once you are on 22 you are supported until mid-2028, so you can clean up old patterns gradually instead of all at once. These free tools help:

You'll find them all on the Angular tools page.


FAQ

When does Angular 20 reach end of life?

On 28 November 2026, when its LTS period ends.

Will my Angular 20 app stop working after end of life?

No. It keeps running, but it gets no security or bug fixes, and newer library versions stop supporting it.

Can I upgrade from Angular 20 straight to 22?

Not in one command. Run ng update for 21 first and then for 22. You can do both in the same day.

Which version should I upgrade to?

Angular 22. It is supported until June 2028, while Angular 21 loses support in June 2027.

When is Angular 23 released?

Around June 2027, under the new yearly release cycle.


Wasim Shaikh

About the author

Wasim Shaikh is a UI/UX developer and front-end engineer with 15+ years of experience, based in Ahmedabad, India. He specializes in Liferay, React, Angular, Next.js and Tailwind CSS.

Keep reading

Web dev · 3 Nov 2026ImageDino vs Bannerbear: A Developer's Guide to Automated Image Generation APIsWeb dev · 10 Oct 2026Angular Moves to Yearly Releases: What It Means for Your UpgradesWeb dev · 7 Oct 2026Agentic Commerce Explained: How AI Agents Shop, Negotiate and Pay for You