Angular Latest Version (May 2026): Current Stable Release & Full Version History

The latest stable version of Angular is Angular 22, released on May 13, 2026. Angular 21 (November 2025) and Angular 20 (May 2025) are also supported under Long-Term Support. If you are searching for the current Angular version in May 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 (May 2026)

Which Angular Version Should You Use?

For new projects starting in May 2026: Use Angular 22. It is the latest stable release with the longest support window (LTS through May 2028).

For existing applications on Angular 21: You are in good shape. Angular 21 LTS runs through May 2027. Plan to upgrade to 22 within the next quarter to stay within the active support window.

For existing applications on Angular 20: Angular 20 LTS runs through November 2026. Upgrade to 21 or 22 before LTS expires.

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 (May 2026)

Angular 22 marks the "signal-first" era. 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.
• OnPush as default. New components use OnPush change 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 valueChanges subscription 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 @defer blocks, introduced in Angular 19 developer preview, is now production-ready.
• Zoneless change detection stabilized in v20.2, enabling Zone.js-free applications.
• resource() and httpResource() 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:

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.

How to Check Your Current Angular Version

Run this command in your project directory:

ng version

This 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.json

If 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/cli

This 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:

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 with specific breaking changes, dependency requirements, and the migration schematics available for each step.

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.