The latest stable version of Angular is Angular 22, released June 3, 2026. Angular 21 (November 2025) is in Long-Term Support through May 2027. Angular 20 (May 2025) is also in LTS through November 2026. If you are searching for the current Angular version in June 2026, Angular 22 is it.
This page is a living reference for Angular version status. It covers which versions are supported, which are end-of-life, and what your team should do based on where you are today.
Angular Version Table (June 2026)
| Version | Released | Active Support Ended | LTS Ended | Status (June 2026) |
|---|---|---|---|---|
| Angular 14 | June 2022 | November 2022 | November 2023 | End-of-life |
| Angular 15 | November 2022 | May 2023 | May 2024 | End-of-life |
| Angular 16 | May 2023 | November 2023 | November 2024 | End-of-life |
| Angular 17 | November 2023 | May 2024 | May 2025 | End-of-life |
| Angular 18 | May 2024 | November 2024 | November 2025 | End-of-life |
| Angular 19 | November 2024 | May 2025 | May 19, 2026 | End-of-life |
| Angular 20 | May 2025 | November 2025 | November 2026 | LTS supported |
| Angular 21 | November 2025 | June 3, 2026 | May 2027 | LTS supported |
| Angular 22 | June 3, 2026 | December 2026 (est.) | May 2028 (est.) | Active support |
Warning
Angular 19 LTS ended on May 19, 2026. If your application runs Angular 19 or anything older, you are running unsupported software. See the Angular end-of-life guide for the security, compliance, and operational risks this creates.
Which Angular Version Should You Use?
For new projects starting in June 2026: Use Angular 22. It is the current stable release in active support through December 2026, with LTS through May 2028.
For existing applications on Angular 21: Angular 21 is now in LTS through May 2027. Upgrade to Angular 22 to stay within the active support window and get the latest features including stable Signal forms and selectorless components.
For existing applications on Angular 20: Angular 20 LTS runs through November 2026. Upgrade to 22 before LTS expires to stay on a supported version.
For existing applications on Angular 19 or older: Upgrade now. Angular 19 LTS ended May 19, 2026. Anything below 19 has been end-of-life for months or years. The Angular upgrade guide covers every version path from 14 to 22 with breaking changes, dependency requirements, and realistic timelines.
What Changed in Recent Angular Versions
Angular 22 (June 3, 2026)
Angular 22 was released on June 3, 2026, marking the "signal-first" era. The current patch release is v22.0.1. Key changes:
- Selectorless components. Components can be imported directly in templates without a selector string, simplifying component composition.
- Signal Forms stable. The new signal-based form system — introduced experimentally in Angular 21 — is now stable. It replaces the reactive forms pattern with a lightweight, signal-driven API.
- Angular ARIA stable. The accessible component patterns package, introduced in developer preview with Angular 21, is now stable.
- OnPush as default. New components use
OnPushchange detection by default, encouraging signal-based reactivity over Zone.js-triggered checks. - MCP server stable. The Angular CLI ships with stable Model Context Protocol support for AI-assisted development tooling.
- Vitest as primary test runner. Vitest is now the default for all new projects, with experimental Jest and Web Test Runner support removed.
Angular 21 (November 2025)
- Zoneless change detection is the default for new projects. Zone.js is no longer included, with change detection driven explicitly by signals.
- Signal Forms introduced as an experimental API — a new form system built entirely on signals, replacing the
valueChangessubscription pattern. - Vitest integration stabilized and became the default test runner, replacing Jasmine and Karma for new applications.
- Angular ARIA package in developer preview for accessible component patterns.
Angular 20 (May 2025)
- Signal primitives graduated to stable —
signal(),effect(),linkedSignal(), signal-based queries and inputs are all production-ready. - Incremental hydration stable — SSR hydration powered by
@deferblocks, introduced in Angular 19 developer preview, is now production-ready. - Zoneless change detection stabilized in v20.2, enabling Zone.js-free applications.
resource()andhttpResource()APIs introduced experimentally for reactive async data fetching.
For teams upgrading from older versions, the most significant architectural shifts happened in Angular 17 (standalone default, new control flow, esbuild builder), Angular 20 (stable signals), and Angular 21 (zoneless default). The Angular Signals enterprise guide covers how to adopt these patterns incrementally.
Angular Release Schedule
Angular follows a predictable 6-month major release cycle:
| Release Window | Version | Expected |
|---|---|---|
| May 2025 | Angular 20 | Released |
| November 2025 | Angular 21 | Released |
| June 2026 | Angular 22 | Released (June 3) |
| November 2026 | Angular 23 | Expected |
Each major version receives:
- 6 months of active support — bug fixes, security patches, and minor feature updates
- 12 months of Long-Term Support (LTS) — critical bug fixes and security patches only
- Total coverage: 18 months from release to end-of-life
This 18-month window moves faster than most enterprise teams expect. Angular 17 felt cutting-edge when it launched in November 2023 with standalone components and the new control flow. By May 2025 — just 18 months later — it was end-of-life.
Note
The 6-month cadence means you can plan upgrades on a predictable calendar. Teams that budget one version upgrade per quarter never fall behind. Teams that defer upgrades accumulate version debt that compounds — each skipped version adds breaking changes, dependency conflicts, and migration effort.
How to Check Your Current Angular Version
Run this command in your project directory:
ng versionThis outputs your Angular CLI version and all @angular/* package versions. The @angular/core version is your framework version.
You can also check directly in package.json:
grep "@angular/core" package.jsonIf your version number starts with 14, 15, 16, 17, 18, or 19, you are running end-of-life software. See the 5 signs your Angular app is falling behind for a broader assessment of your application health.
How to Upgrade to the Latest Angular Version
Angular supports upgrading one major version at a time using the ng update command:
ng update @angular/core @angular/cliThis runs migration schematics that automatically update your code for breaking changes where possible. You cannot skip versions — going from Angular 17 to 22 requires five sequential upgrades: 17 → 18 → 19 → 20 → 21 → 22.
Realistic timelines from enterprise projects (target: Angular 22, current stable):
| Starting Version | Target | Steps | Typical Duration |
|---|---|---|---|
| Angular 21 → 22 | 22 | 1 upgrade | 1-2 weeks |
| Angular 20 → 22 | 22 | 2 upgrades | 2-4 weeks |
| Angular 19 → 22 | 22 | 3 upgrades | 3-6 weeks |
| Angular 18 → 22 | 22 | 4 upgrades | 1-2 months |
| Angular 17 → 22 | 22 | 5 upgrades | 2-3 months |
| Angular 16 → 22 | 22 | 6 upgrades | 2-4 months |
| Angular 14 → 22 | 22 | 8 upgrades | 3-6 months |
These timelines are from 19 enterprise migration projects and include dependency updates, testing, and CI/CD pipeline adjustments. Small applications are faster. Large monorepos with custom build configurations take longer.
The Angular upgrade guide covers every version path from 14 to 22 with specific breaking changes, dependency requirements, and the migration schematics available for each step.
Note
Separate the version upgrade from pattern modernization. Get to a supported version first, then adopt signals, zoneless change detection, and signal forms incrementally. Combining both into one project is the most common reason Angular migrations fail.
Wondering where your Angular app stands? Take the free 3-minute modernization scorecard →
Staying Current Going Forward
The simplest way to avoid version debt is to upgrade within the first quarter after each new Angular release. With a 6-month release cadence, that means two planned upgrades per year — each taking 1-2 weeks for a single-version jump.
If you are multiple versions behind and need help planning the upgrade path, the free Angular modernization assessment evaluates your application across five dimensions and gives you a prioritized roadmap in three minutes. For hands-on upgrade support, see our Angular consulting services.