Angular Lifecycle Intelligence

Angular End of Life & Support Options —
What To Do When Angular Patches Stop, Every Version's Date

By Scott Bissett Updated September 5, 2026 · endoflife.ai · 8 min read

Angular — the TypeScript framework, versions 2 through 22 — spent a decade on one of the shortest support windows in mainstream front-end development: about 18 months per major version, with a new major every six months and a version reaching end of life every six months too. That cadence ended with Angular 22, released June 3, 2026: majors now ship once a year and each is supported for about 24 months. The older versions still run out on the old clock. Angular 19 reached end of life on May 19, 2026, Angular 20 follows on November 28, 2026, and Angular 21 on June 30, 2027.

This is a different product from AngularJS (1.x), which is a separate, fully end-of-life framework — don't confuse the two. This page covers modern Angular (2+): every version's EOL date and EOL Risk Score™, why teams fall behind so fast, the ng update path forward, and extended-support options for versions you can't move off yet.

Quick answer: Angular 20 support ends November 28, 2026; its active support ended November 19, 2025, so 20 receives security fixes only until then. Angular 21 active support ended June 3, 2026 and its end of life is June 30, 2027. Angular 22, released June 3, 2026, is the current version, with end of life June 30, 2028. Every other version's EOL date is in the schedule below.
In this article
  1. Angular version EOL schedule — every release
  2. Every Angular version, one line each
  3. The support policy — 24 months from Angular 22, 18 months before it
  4. Angular 20, 21 & 22 — the supported versions
  5. How to stay current with ng update
  6. Extended support for older Angular

Key Dates at a Glance

Angular Version EOL Schedule

Every Angular major from 2 through 19 is now end of life. Only 20, 21, and 22 are within their support window; versions before 9 predate the dates Angular publishes and are omitted. Scores below are live EOL Risk Scores™ — click any to see the full breakdown.

Version Released Active support ends End of Life Status EOL Risk Score™
Angular 22 (latest) Jun 3, 2026 Jun 30, 2027 Jun 30, 2028 Supported 20
Angular 21 Nov 19, 2025 Jun 3, 2026 Jun 30, 2027 Approaching 20
Angular 20 May 28, 2025 Nov 19, 2025 Nov 28, 2026 Approaching 35
Angular 19 Nov 19, 2024 May 28, 2025 May 19, 2026 EOL 50
Angular 18 May 22, 2024 Nov 19, 2024 Nov 21, 2025 EOL 50
Angular 17 Nov 8, 2023 May 8, 2024 May 15, 2025 EOL 55
Angular 16 May 3, 2023 Nov 8, 2023 Nov 8, 2024 EOL 55
Angular 15 Nov 16, 2022 May 3, 2023 May 18, 2024 EOL 60
Angular 14 Jun 2, 2022 Nov 18, 2022 Nov 18, 2023 EOL 60
Angular 13 Nov 3, 2021 Jun 2, 2022 May 4, 2023 EOL 60
Angular 12 May 12, 2021 Nov 12, 2021 Nov 12, 2022 EOL 60
Angular 11 Nov 11, 2020 May 11, 2021 May 11, 2022 EOL 60
Angular 10 Jun 24, 2020 Dec 24, 2020 Dec 24, 2021 EOL 60
Angular 9 Feb 6, 2020 Aug 6, 2020 Aug 6, 2021 EOL 60
Angular 19 reached EOL on May 19, 2026. If you are on 19, you are now outside the support window — no more official patches, including security fixes. Angular 20 is supported until November 28, 2026, Angular 21 until June 30, 2027, and Angular 22 — the current release — until June 30, 2028. From Angular 22 on, with one major a year and 24 months of support, being one version behind is sustainable; being two behind is not.
Running Angular past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers Angular is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

Every Angular version, one line each

The same schedule as plain statements, one per major, for anyone who needs a single date rather than a table. Every date is bound to the same data as the Angular product page, checked against the versioning and releases page on angular.dev, and re-verified at each build. Versions before Angular 9 are not listed.

The Support Policy — 24 Months From Angular 22, 18 Months Before It

Angular's support model is fixed and predictable — which is exactly what makes falling behind inexcusable, and also exactly why so many teams do.

From Angular 22 on, each major gets about 24 months of support, split in two: 12 months of active support (regularly scheduled updates and patches) followed by 12 months of long-term support (LTS) (critical fixes and security patches only). A new major ships once a year; Angular's published schedule places Angular 23 about a year after 22. Angular 22 itself, released June 3, 2026, leaves active support on June 30, 2027 and reaches end of life on June 30, 2028.

Every version up to Angular 21 was released under the old policy: about 18 months of support (6 months active, 12 months LTS) with a new major every six months, historically around May and November. Those dates do not move. Angular 20, released May 28, 2025, reaches end of life on November 28, 2026; Angular 21, released November 19, 2025, on June 30, 2027. The arithmetic that made Angular a treadmill — three supported majors at once, one dropping off every six months — applied to a decade of releases, and it is why so many production apps are stranded several majors back today.

The new cadence slows the treadmill; it does not stop it. A team that ships on Angular 22 and then focuses on features for two years will be at end of life without having changed a line of framework code. Unlike a five-year database cycle, Angular still demands a standing, scheduled upgrade habit — now once a year rather than twice.

Angular 20, 21 & 22 — The Supported Versions

Angular 20, 21 & 22
20 → EOL Nov 28, 2026 · 21 → EOL Jun 30, 2027 · 22 → EOL Jun 30, 2028
35
EOL Risk Score™

Angular 22 is the current release and the right target for any upgrade today — it carries the longest runway, to June 30, 2028. Angular 21 (Risk Score 20) is supported until June 30, 2027, and Angular 20 (Risk Score 35) until November 28, 2026 — reasonable interim stops if a jump straight to 22 is not yet practical.

Modern Angular has steadily reduced upgrade pain: standalone components removed the NgModule boilerplate, the new control-flow syntax and signals modernised the template and reactivity layers, and the ng update tooling automates most of the mechanical migration between adjacent majors. The framework moves fast, but it also gives you better tools to keep up than it used to.

The rule on Angular: there is no "settle here for years" version. Pick the latest, and budget a recurring upgrade every twelve months. That is the cost of the framework — pay it on schedule, not in an emergency.

How to Stay Current with ng update

Angular is designed to be upgraded one major at a time, and the CLI does most of the work. The failure mode is not the mechanics — it is letting too many versions pile up so the jumps compound.

What to do about it

Angular currently carries an EOL Risk Score™ of 50/100 — Grade C, elevated risk, recalculated at every site build from EOL recency, attack surface, CISA KEV exposure, and extended-support availability. Per-version scores and dates are on the Angular lifecycle page.

The right response comes down to one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support fees paid repeatedly cost more than doing the project once. Indefinitely, migrate now and plan the next one before it surprises you. Extended support is often the more expensive choice over a multi-year horizon — a bridge, not a destination. And if this deadline feels like vendor caprice, it isn’t — why end of life is inevitable for every version, with the receipts.

Extended Support for Older Angular

Plenty of production Angular apps are stranded several majors back — often on Angular 12–16 — because an upgrade was deferred until the cumulative gap became a daunting project. Those apps are now running EOL framework code, shipping unpatched to every user's browser; their live Risk Scores are on the version pages linked above.

Extended (post-EOL) support bridges that gap. Specialist vendors maintain security-patched builds of older Angular majors — backporting fixes for newly disclosed vulnerabilities — so a stranded app stays protected while you plan a staged path back to a supported version. It buys you a safe runway to do the ng update work properly instead of under incident pressure.

The pragmatic path Use extended support as a bridge, not a destination. It keeps an older Angular app patched while you climb back to a supported major on a realistic schedule. Compare the providers and what each covers on our extended-support partners page.

Check your whole front-end stack for EOL exposure

Angular is one dependency. Check your runtime, build tooling, and the rest of your stack too — free, no signup required.

Scan your stack Check a version Extended support options
Related articles

Frequently Asked Questions

Which Angular versions are supported right now?

Angular 22 (released June 3, 2026, in active support until June 30, 2027, then long-term support to June 30, 2028), Angular 21 (in its long-term-support phase until June 30, 2027) and Angular 20 (in its long-term-support phase until November 28, 2026). Angular 19 reached end of life May 19, 2026 and Angular 18 on November 21, 2025.

How long is each Angular version supported?

From Angular 22 on, about 24 months: twelve months of active support (regular updates and patches) followed by twelve months of long-term support (critical fixes and security patches only), with a new major once a year. Versions up to Angular 21 were released under the previous policy of about eighteen months (six active, twelve LTS) with a new major every six months; their dates are unchanged.

When does Angular 20 reach end of life?

November 28, 2026. It left active support on November 19, 2025 when Angular 21 shipped and has been in LTS since. Applications on 20 should be on 22 (or at least 21) before that date; ng update handles most of the move.

What happens to an Angular app after its version reaches end of life?

The framework keeps running, but security fixes stop and the CLI, Material and CDK packages for that major stop moving too, so dependency updates start failing. Third-party vendors sell continued security patches for end-of-life Angular majors — and for AngularJS (1.x), end of life since January 2022 — as a bridge for applications that cannot upgrade yet.

When does Angular 21 reach end of life?

June 30, 2027. Angular 21 was released November 19, 2025 and left active support on June 3, 2026, the day Angular 22 shipped; it is in long-term support until its end-of-life date.

Is Angular 18 still supported?

No. Angular 18 reached end of life on November 21, 2025, Angular 17 on May 15, 2025 and Angular 16 on November 8, 2024. None of them receives security fixes from the Angular team. The supported majors are 20, 21 and 22.

When is Angular 23 released?

Angular's published schedule targets Angular 23 about one year after Angular 22, which shipped June 3, 2026 — the first release on the annual cadence. Until it ships, Angular 22 is the current major, with minor releases roughly every two months.

Is there extended support for Angular 18 or 19 after end of life?

Not from the Angular team, whose support ends on the end-of-life date. Commercial vendors sell security patches for end-of-life Angular majors, usually priced per year, as a bridge for applications that cannot upgrade in time. Whether a bridge beats an upgrade depends on how long the application has left to run and how many majors it is behind; the form on this page matches options.

The Monthly EOL Digest™

Once a month — critical end-of-life dates, CVE blind spots, and lifecycle changes worth knowing about.