Angular 23 release date: June 2027, a 12-month cycle and v21 LTS end

Summary. Angular 23 is scheduled for about June 2027, the first major under Angular's new model: one major every 12 months instead of every six, 4 to 6 minors per major, and about 24 months of support, 12 active and 12 in long-term support (LTS). Until v22, majors came every six months with 1 to 3 minors and 18 months of support. Angular 21, released on 19 November 2025, is in LTS until June 2027, so its security fixes stop in the month v23 is due. Angular 22, released on 3 June 2026, stays active until June 2027 and in LTS until June 2028. Angular 20 leaves LTS on 28 November 2026, three weeks from now. Because ng update moves one major at a time, every v20 or v21 app should reach v22 before June 2027. That hop is not small: v22 requires TypeScript 6.0 and Node.js 22.22.3, 24.15.0 or 26, makes components without a change detection setting OnPush, and deprecates the Webpack-based builders, which become candidates for removal from v23. Angular has not published v23's features or requirements, and calls its dates guidance that can change.

About this article. For engineering managers, architects and developers who need a dated Angular upgrade plan for 2027. On 7 November 2026 we checked every date, version and requirement against Angular's versioning, compatibility, roadmap and CLI pages, the Angular blog, the angular/angular GitHub release notes and the Node.js release schedule, and, for the regulatory notes, the DPDP Rules, 2025 as published on 13 November 2025 (G.S.R. 846(E)) and the GDPR on EUR-Lex. v23 details are pre-release. This is general information, not legal advice, and no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.

What is confirmed for Angular 23, and what is not

This is what Angular had published on 7 November 2026, across its versioning and compatibility pages, the v22 announcement and GitHub releases.

Angular gives the v21 and v22 end dates to the month only. Treat 1 June 2027 as the v21 deadline, not 30 June. Angular 20 is the exception, with a fixed LTS end of 28 November 2026. The v21 date has already moved once: before the cadence change, Angular's table showed v21 active until 19 May 2026 and in LTS until 19 May 2027.

The release cadence change, old versus new

Angular's current versioning page gives the new policy and notes the old six-month cycle; an archived copy from November 2025 shows the old policy in full, including 18 months of support and deprecations kept for at least two majors.

The 8-week minor rhythm comes from angular.love's explainer of 5 August 2026; Angular's own page gives only the 4 to 6 count. The v20 row in Angular's support table confirms the old length: released 28 May 2025, out of LTS on 28 November 2026, which is 18 months.

Some rules stay the same: breaking changes land only in majors, minors only widen peer dependency ranges, and ng update works only when the target is supported and within one major of your current version. v21 straddles the transition, with about six and a half months active and about 19 months in total. v22 is the first major with the full 24 months.

Angular support matrix on 7 November 2026

Dates come from the versioning page, and Node.js and TypeScript ranges from the compatibility page. The v23 row is our projection from the 12 plus 12 policy, not a published commitment.

LTS means narrow fixes. Angular considers an LTS fix only for a newly identified security vulnerability, or for a regression since the start of LTS caused by a third-party change such as a new browser version. Feature work and ordinary bug fixes stop when a major leaves active support.

Two columns cause most upgrade failures. Angular 22 dropped Node.js 20 and needs at least 22.22.3 or 24.15.0, so older CI images fail before any code compiles, while v21 does not accept Node.js 26. Node.js 22 reaches end of life on 30 April 2027, about a month before v23 is due; Node.js 24 is supported to 30 April 2028, and Node.js 26, in LTS since 28 October 2026, to 30 April 2029. Our Node.js 22 end-of-life guide covers that move, and we would not plan on v23 accepting Node.js 22. TypeScript bands are narrow too: v22 requires 6.0.x, and the page still shows a single 22.0.x row although v22.2 has shipped, so recheck it before each minor.

Browser support is defined by a date: Angular supports the Baseline widely available set, meaning browsers released in the 30 months before 7 May 2026 for v22, 20 October 2025 for v21 and 30 April 2025 for v20, which Angular says covers about 95% of web users. If your audience includes older Android phones, check your analytics against that set before each major.

What June 2027 means for the version you run

On v20. LTS patches still matter. Release 20.3.34, published on 14 October 2026, carried an HTTP fix that enables XSRF protection for same-origin absolute URLs, and 20.3.35 followed on 2 November. Fixes like these stop after 28 November 2026.

On v21. Wait for v23 and v22 will already be in LTS, with another upgrade due within 12 months. Moving now gives you v22's remaining minors (22.3 to 22.5) and a year to plan v23.

On v22. Let v23 wait for its first patches and your libraries.

What the 12-month cycle means for enterprise upgrade planning

The change halves the number of framework migrations a team must schedule. From v21 to the end of 2027, the old six-month rhythm would have meant four more majors (v22 to v25); the published schedule means two (v22 and v23). That is arithmetic on the stated cadences, not an Angular forecast.

Five planning points follow; the judgements in them are ours.

1. One budgeted upgrade a year. A June major lands at the end of the first quarter of India's April to March financial year, and at the end of Q2 for calendar-year budgets. Reserve engineering time in the quarter after each June release instead of squeezing majors into feature sprints.

1. Expect more per major, not less. The minimum deprecation period is still about 12 months, so each major can carry a full year of removals. Fewer upgrades does not mean smaller ones. Clear deprecation warnings during the 4 to 6 minors, while the code still compiles both ways.

1. Staying one major behind is now a clear policy. Each major is active for 12 months, then in LTS for the next 12 while its successor is active. Staying one major behind keeps you supported, but on LTS you get critical and security fixes only, not ordinary bug fixes.

1. Libraries set the real date. Design systems and third-party component libraries must support the new major before apps can move. Upgrade your shared library first, and check each external library's peer dependency range on npm before committing to a date.

1. Align toolchains to the same calendar. Node.js also moves to one major a year with Node.js 27 on 22 April 2027, eight days before Node.js 22 ends, as our guide to the Node.js annual release model explains. One planned window for Node.js, TypeScript and Angular costs less than three unplanned ones.

What to watch before v23 ships

None of these is confirmed for v23. They are what Angular has deprecated, previewed or started.

The compiler work exists because Angular's compiler applies its own code transformations through TypeScript's ts.Transformer API, which the Go-compiled TypeScript 7 does not expose across languages, according to Angular's September 2026 update. TypeScript 7.0 itself shipped on 8 July 2026. Our TypeScript 7 migration guide covers the wider toolchain. The application builder came with the v17 build system and is the default for new applications.

The v21 to v22 changes that bite

These breaking changes from the 22.0.0 release notes are the ones most likely to surface in enterprise code; the notes list more.

The update does some of this for you: the 22.0.0 notes list migrations that add ChangeDetectionStrategy.Eager where applicable, switch off the two nullability diagnostics, add strictTemplates, keep HttpXhrBackend for existing provideHttpClient calls and update CanMatch guards. The OnPush default still deserves its own test pass. A component that mutates an input object in place, or relies on a parent's event to refresh it, can stop updating without any error. Visual regression and end-to-end tests catch this; unit tests often do not.

Runbook: v21 to v22 now, v22 to v23 next year

ng update takes the form ng update @angular/cli@^<major> @angular/core@^<major>, and Angular recommends taking the latest patch of your current major first. It refuses to run on a repository with modified or untracked files unless you pass --allow-dirty.

            # 1. Confirm versions and a clean working tree
ng version
node --version
git status

# 2. Take the latest patch of your current major first
ng update @angular/cli@^21 @angular/core@^21

# 3. Move one major, with a commit per migration
ng update @angular/cli@^22 @angular/core@^22 --create-commits

# 4. Update other Angular packages you use, such as Material and CDK
ng update @angular/material@^22

# 5. Build, test and read every new diagnostic
ng build
ng test
          

Around those commands:

1. Fix the runtime first. Move CI images and developer machines to Node.js 24.15.0 or later, which both v21 and v22 accept, and record each Angular library's peer dependency range. Move to Node.js 26 only after the v22 hop, because v21 does not support it.

1. Review commit by commit. The --create-commits option makes each migration a separate commit. Check change detection, router configuration and removed factory APIs before running tests.

1. Use the escape hatches sparingly. The --migrate-only option with --from and --to re-runs one package's migrations without changing installed versions. The --force option ignores peer dependency mismatches; use it only for a library you have tested.

1. Test in layers, then release gradually. Unit and end-to-end tests, visual regression, server-side rendering and hydration, bundle budgets, then a canary.

1. Prepare v23 during v22. Clear deprecation warnings in each v22 minor and move off the Webpack builders. When v23 ships, repeat with ^23 after its first patches.

Pick your path

Worked example: an estate of 10 Angular apps

Assume an organisation runs 10 Angular apps, 4 on v20 and 6 on v21, and, as an illustration, that each hop costs 3 engineer-days for review, testing and release.

Before June 2027. The v20 apps need 2 hops each and the v21 apps 1: (4 × 2) + (6 × 1) = 14 hops, and 14 × 3 = 42 engineer-days. From Monday 16 November 2026 to Friday 28 May 2027 is 28 working weeks, so the work needs 42 ÷ 28 = 1.5 engineer-days a week. The four v20 apps run without upstream fixes from 28 November 2026 until their first hop lands, so schedule them first.

After June 2027. Under the annual cadence the same 10 apps need 10 hops a year, or 10 × 3 = 30 engineer-days. Under the old six-month rhythm they would have needed 20 hops, or 20 × 3 = 60 engineer-days. If each major now carries a year of changes and costs 4 days instead of 3, the annual figure is 10 × 4 = 40 engineer-days, still a third below the old 60.

India and EU notes

India. Rule 6 of the DPDP Rules, 2025, on reasonable security safeguards, comes into force eighteen months after publication on 13 November 2025, so on 13 May 2027, 19 days before 1 June 2027. The Rules name no software versions, but an unsupported customer-facing framework is a weak position to defend under that duty. Our DPDP Rules checklist covers the wider controls. If an outside vendor maintains your Angular apps, write the supported-version requirement into the contract.

EU. GDPR Article 32 asks for security appropriate to the risk, taking account of the state of the art, without naming software versions. A dated upgrade plan is simple evidence under both.

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our Angular development team runs Angular estate audits, one-major-at-a-time upgrades with regression and visual tests, Webpack-to-application-builder migrations and CI version matrices for Node.js and TypeScript. Talk to us at /contact-us/.

Last updated: 7 November 2026.

References

1. Versioning and releases — Angular

1. Versioning and releases, archived copy of 27 November 2025 — Angular, via the Internet Archive

1. ng update, CLI reference — Angular

1. Version compatibility — Angular

1. Release 22.0.0 — angular/angular on GitHub

1. Announcing Angular v22, 3 June 2026 — Angular Blog

1. Releases — angular/angular on GitHub

1. Angular new release cycle: release schedule change explained, 5 August 2026 — angular.love

1. Node.js release schedule (schedule.json) — Node.js Release Working Group on GitHub

1. Release 20.3.34, 14 October 2026 — angular/angular on GitHub

1. Roadmap — Angular

1. Error boundaries with @boundary — Angular

1. Release 22.2.0, 23 September 2026 — angular/angular on GitHub

1. An update on Angular's TypeScript 7-powered compiler, September 2026 — Angular Blog

1. Announcing TypeScript 7.0, 8 July 2026 — Microsoft TypeScript blog

1. Angular application build system — Angular

1. Digital Personal Data Protection Rules, 2025, G.S.R. 846(E), 13 November 2025 — Ministry of Electronics and Information Technology

1. Regulation (EU) 2016/679 (General Data Protection Regulation), Article 32 — EUR-Lex