Angular 20 end of life on 28 November 2026: which version to upgrade to

Angular 20 receives security fixes until 28 November 2026. After that date, Google’s Angular team no longer publishes anything for this version. This guide gives the exact dates, what end of life changes, the version to upgrade to, the order of the updates and the changes to check between Angular 20 and Angular 22.

It is written for technical leaders, CIOs and application owners whose front end still runs on Angular 20. Upgrading web applications is part of our web development and application maintenance offers.

When does Angular 20 support end?

Angular 20 support ends on 28 November 2026, at the end of its long-term support period. The rule is published by the Angular team: a major version is generally supported for 24 months, that is 12 months of active support with regular updates, then 12 months of long-term support, limited to critical and security fixes.

Angular 20 was released on 28 May 2025. Its active support ended on 19 November 2025, when Angular 21 came out; since then, it has only received security and regression fixes. Its latest release to date is 20.3.35, of 2 November 2026.

Angular versions 2 to 19 are no longer supported: an application still on Angular 19, or older, is already in the situation awaiting Angular 20.

What happens after 28 November 2026?

After 28 November 2026, an Angular 20 application keeps running normally, but no vulnerability discovered afterwards in the framework will be fixed for it. Nothing breaks on 29 November: the risk grows, as fixes are only published for Angular 21 and 22.

• Security. Long-term support covers precisely newly identified vulnerabilities. After 28 November, a vulnerability that also affects Angular 20 stays open.
• Browsers. During long-term support, the Angular team also fixes regressions caused by an external change, such as a new browser version. That protection ends at the same time.
• Dependencies. Component libraries and tools follow recent versions: an application left on Angular 20 gradually gets stuck on old versions of its dependencies.
• Your clients’ and auditors’ requirements. If a contract, a client or a security audit requires supported components, Angular 20 becomes a gap to justify.

Third-party companies sell paid support for Angular versions that are out of official support. It buys time, not a solution: the upgrade still has to be done. The approach is the same as for a server-side language reaching end of life, described in our article on the end of support for PHP 8.2.

Angular 21 or Angular 22: which version to upgrade to?

To leave Angular 20, the preferred target is Angular 22: it is the active version, released on 3 June 2026, and it will be supported until June 2028.

• Angular 22, the default choice. Supported until June 2028. Features introduced in Angular 21 have become stable there, notably signal-based forms and the resource APIs: new screens no longer rely on experimental APIs.
• Angular 21, a step, not a target. It is already in long-term support and ends in June 2027: stopping there means doing the same work again in seven months.
• Angular 21 as a temporary target, only if a component requires it. When an essential library is not yet compatible with Angular 22, or when the environment cannot yet move to TypeScript 6 or leave Node.js 20.

Can you go straight from Angular 20 to Angular 22?

No: the ng update command only moves one major version at a time. To go from Angular 20 to Angular 22, you first move to Angular 21, then to Angular 22.

If you ask for a jump of several major versions, the tool stops with the message “Updating multiple major versions … at once is not supported” and gives the command to run for the next version. Each step applies the automatic migrations of its version, which rewrite the code where a behaviour changes: skipping them would mean doing them by hand.

The two commands, in order: ng update @angular/cli@21 @angular/core@21, then, once version 21 has been tested, ng update @angular/cli@22 @angular/core@22. The Angular team’s interactive update guide lists, for each step, the points to check depending on the complexity of the application.

How do you upgrade from Angular 20 to Angular 22?

An upgrade from Angular 20 to Angular 22 is done in two successive updates, each tested before the next, after bringing the environment up to date. The steps, in order:

• Take stock. Exact Angular version, Node.js and TypeScript versions, component libraries and their compatibility with Angular 21 and 22, test tooling, build chain. A quick audit of the existing setup answers these questions.
• Bring the environment up to date. Angular 22 accepts Node.js 22.22.3, 24.15 or 26, and no longer Node.js 20; TypeScript 5.9 for Angular 21, then TypeScript 6 for Angular 22. Continuous integration servers and deployment images are affected too.
• Move to Angular 21. Run ng update, review the migrations applied, build the application and run the tests.
• Move to Angular 22. The same, then handle by hand what the migrations do not cover, starting with the router (see the next section).
• Test the application. Critical user journeys, forms, navigation, server calls, and server-side rendering if used. A test campaign prepared before the upgrade serves as the reference.
• Ship and monitor. An announced production release, with a rollback ready, then monitoring of the errors reported by browsers.

What changes between Angular 20 and Angular 22?

Between Angular 20 and Angular 22, most behaviour changes are covered by automatic migrations that keep existing behaviour. A few points still need checking, or a manual fix.

Moving to Angular 21:

• Zoneless by default. New applications no longer use Zone.js to detect changes. For an existing application that relies on it, the migration adds provideZoneChangeDetection(): its behaviour does not change. Actually dropping Zone.js is a separate project, to be planned.
• Vitest for tests. New projects use Vitest; Karma remains usable but is deprecated, and an optional migration converts Jasmine tests. Tests that use fakeAsync have to be rewritten by hand.
• HttpClient provided by default. provideHttpClient() is now only needed to customise the client, for example to add interceptors.
• TypeScript 5.9. Angular 21 requires at least TypeScript 5.9.

Moving to Angular 22:

• TypeScript 6 and Node.js. Angular 22 requires TypeScript 6 and drops Node.js 20. As Node.js 22 is itself only supported until 30 April 2027, aim for Node.js 24 or 26.
• OnPush by default. The default change detection strategy becomes OnPush. The migration adds the Eager strategy, formerly “Default”, to components that did not declare one, to keep their behaviour.
• HttpClient on the Fetch API. The HTTP client now uses Fetch; the migration adds withXhr() where the old implementation must be kept. Upload progress is not supported with Fetch.
• Strict template checking. strictTemplates is enabled by default; the migration explicitly disables it where it was not enabled. Turning it on afterwards surfaces useful type errors.
• The router. paramsInheritanceStrategy now defaults to “always”: child routes inherit their parents’ parameters. No migration is provided: to keep the old behaviour, set “emptyOnly” by hand.
• Optional chaining in templates. An expression such as project?.author now returns undefined instead of null, as in TypeScript; a migration wraps the affected expressions.
• Webpack. The webpack-based builder (@angular-devkit/build-angular) is deprecated: an application still using it should move to Angular’s “application” builder.

An application that has fallen behind on its versions often hides other delays, in the code as in the infrastructure: it is part of technical debt, and catching up is a matter of evolutive maintenance.

Frequently asked questions

Angular 20: set the upgrade date now

28 November 2026 breaks nothing, but it opens a period in which every vulnerability discovered in the framework stays open on Angular 20. The decision comes down to three points: the target version (Angular 22), the order of the steps (21, then 22), and a release date for each, set after the dependency inventory.

The iones team upgrades Angular applications, from the inventory to production, as part of its web development offer, and keeps them up to date over time with application maintenance. To review your applications, write to us.