Angular Versions: History, Latest Features, and Upgrade Paths in 2026

Angular has evolved from AngularJS 1.x all the way to Angular 22, with regular, predictable releases along the way. Knowing which version your project runs on, what changed since then, and how long you have before support runs out is essential for planning upgrades and managing technical debt.

This guide walks through Angular’s release history, what’s new since Angular 19, and how to plan an upgrade — whether you’re a few versions behind or migrating from AngularJS.

Key Takeaways

• Angular 22, released June 3, 2026, is the latest stable version, continuing a predictable six-month release schedule.
• Each major Angular release is supported for 18 months — 6 months of active support followed by 12 months of long-term support (LTS) — which is why staying current matters for security.
• Recent versions introduced signals for reactive updates, zoneless change detection, a modernized CLI, the Angular MCP server for AI-assisted development, and Angular Material enhancements that reshape how applications are architected.
• Clear upgrade paths exist through ng update tooling and the official Angular update guide — you don’t have to guess your way through a migration.

Why Angular Versions Matter Today

Angular is a Google-backed framework that has evolved from AngularJS 1.x to Angular 22 with regular, predictable releases. Every major version brings performance, developer experience, and maintenance improvements — but it also starts a support clock. Falling behind means missing security patches once your version reaches end of life.

House of Angular specialists help teams navigate these version transitions without disrupting production, and the Angular Evolution Guide, maintained by House of Angular together with the angular.love community, tracks every release in detail.

Release Cadence and Support Model

Angular follows semantic versioning, with major releases arriving roughly every six months — typically in May and November. Angular 20 was released in May 2025, Angular 21 on November 20, 2025, and Angular 22 on June 3, 2026.

Support windows span 18 months total: six months of active development support, followed by twelve months focused exclusively on critical security patches. Typically, 2–3 versions are supported at the same time.

Angular Evolution Timeline

AngularJS Era (2010–2018)

Introduced dependency injection, two-way data binding, and MVC/MVVM patterns. Official support for AngularJS ended on December 31, 2021 — if you’re still running it, there are no further security patches coming.

Angular 2–8 (2016–2019)

A complete framework rewrite emphasizing components, TypeScript adoption, improved compilation, and the HttpClient module. (Angular 3 was skipped, to align the framework and router versions.)

Ivy Era (2020–2021)

Angular 9 established the Ivy compiler as the default rendering engine, enabling smaller bundles, improved change detection, and better debugging. Angular 13 later removed legacy View Engine support entirely.

Modern Standalone Era (2023–2024)

Angular 17 made standalone components the default in new projects, eliminating the need for NgModules in many Angular applications. Control flow syntax replaced structural directives, and Angular 18 refined deferrable views for lazy rendering.

Angular 19–22: The Signals and AI Era

Angular 19 (2024)

Enhanced signals capabilities with linkedSignal and refined effect timing. Angular 19 reaches end-of-life on May 19, 2026 — if you’re still on it, now is the time to move.

Angular 20 (May 2025)

Stabilized the signals API and pushed zoneless change detection toward default status. Teams migrating reported roughly an 8–12% reduction in initial bundle size.

Angular 21 (November 2025)

Made zoneless change detection the default for new projects. Signal forms entered developer preview with improved typing, and Vitest replaced Karma as the testing default. The Angular MCP server also arrived, integrating AI workflows for smart refactoring, migration assistance, and workspace-aware suggestions.

Angular 22 (June 2026)

Stabilizes signal forms, introduces selectorless components, and extends zoneless ecosystem support across third-party libraries.

Angular Material Evolution

Material versions align with framework versions — Material 21 ships alongside Angular 21, and so on. During the Ivy era (v9–12), Material gained tree-shakeable modules, improved theming, and better accessibility patterns. The v19–21 period brought signals compatibility and enhanced SSR support.

Critical Breaking Changes

Major version upgrades introduce breaking changes that require migration planning:

• Angular 13: ViewEngine removal forced library updates across the ecosystem.
• Angular 19–21: Long-deprecated API removal, NgModuleFactory elimination, and default OnPush strategy adoption.
• Common pain points: tests relying on ng-reflect-* attributes, outdated lazy-loading syntax, and HammerJS dependencies.

Upgrade Strategies

Teams on v19–20: upgrading to Angular 21 typically takes hours to a few days with ng update, following the standard procedure.

Teams on v16–18: plan staged upgrades across multiple major versions, adopting the new control flow syntax and resolving dependency-injection deprecations incrementally.

Teams on v15 and earlier: this is a modernization project, not a quick upgrade — expect weeks of work, including module refactoring, CLI configuration updates, and polyfill replacement.

Don’t migrate immediately without a plan when handling very old versions. House of Angular typically starts with a comprehensive audit examining the dependency graph, Material usage, test coverage, and performance characteristics before touching any code. If you want a second opinion on where your project stands, see how we plan Angular upgrades in practice.

Migration Tooling

Run ng update @angular/core @angular/cli to execute automated schematics and generate migration notes, then follow with ng update @angular/material for the component library. The Angular MCP server is a newer capability that gives AI tools full workspace context to propose targeted refactors and migration plans.

Architecture Across Versions

Dependency injection started with NgModules as DI boundaries; modern versions enable component-level configuration with tree-shakeable providers and stronger type safety.

Change detection was originally powered by Zone.js; modern signals enable fine-grained reactivity without global monkey-patching, and OnPush strategy adoption continues to grow.

The Angular Evolution Guide

House of Angular’s free ebook consolidates resources addressing real challenges: code bugs, performance slowdowns, UX regressions, and maintenance overhead. It includes version comparison tables, ng update checklists, and multi-major-version migration strategies you won’t find elsewhere in one place.

Recommendations for New and Existing Projects

New projects should launch on Angular 22, or at minimum Angular 21, to get signals, zoneless change detection, and current Material defaults from day one.

Existing applications should evaluate their current version’s support status, the team’s familiarity with modern patterns, test coverage quality, and business risk tolerance. If your project is on v19 or v20, move to Angular 21 now to benefit from current tooling and security patches rather than waiting.

Support Status in Mid-2026

• Angular 22 — active support.
• Angular 21 — long-term support, extending through late 2027.
• Angular 20 — LTS until November 2026.
• Angular 19 — supported until approximately May 19, 2026.
• v2–v18 and AngularJS — no updates or security patches.