Angular 22 shipped in June 2026 and the current line is 22.2.x. The release focuses on stabilization. Applications built with standalone components, NgRx, RxJS and zoned change detection can continue with their existing architecture.

npx ng update @angular/core@22 @angular/cli@22
npx ng update

Three previously experimental APIs are now stable. Signal Forms provides reactive forms built on signals. Async Signals use the resource pattern for server state. Angular Aria supplies headless primitives for accessible interfaces. The stable status supports longer-lived documentation, more predictable import paths across minor releases and enterprise adoption.

Working Reactive Forms and effects do not require a migration. The article recommends Signal Forms for new forms, with validation handled in TypeScript. NgRx Store and Effects remain suited to global client state, complex workflows, undo and offline queues. Async Signals fit server caches for user profiles, lists and detail pages. Plain signals, computed and effect remain suitable for local UI state such as dialogs, filters and language settings. v22 leaves the choice between these approaches open, while new fetch-and-display work can use Async Signals without adding an effect.

The v21 example boots `App` through `bootstrapApplication` with `appConfig`. Its providers include `provideBrowserGlobalErrorListeners`, `provideZoneChangeDetection({ eventCoalescing: true })`, `provideRouter(routes, withInMemoryScrolling({ scrollPositionRestoration: 'enabled' }))`, `provideStore(reducers, { metaReducers })`, `provideEffects([UserEffects, MenuEffects])` and `provideClientHydration(withIncrementalHydration(), withEventReplay())`. Components can already combine `signal` and `effect`, as shown by `showDeleteDialog = signal<boolean>(false)` and `language = signal<string>('en')`.

Angular 22 continues work on control flow, deferrable views and hydration. Incremental hydration with event replay can make server-rendered pages interactive sooner while preserving clicks that occur during hydration. The suggested readiness check covers standalone components, `@if`, `@for` and `@defer` in place of `*ngIf` and `*ngFor`, plus a clean hydration report in DevTools.

The supported upgrade route covers 21.0 to 22.0 through Angular’s update guide. In a monorepo, update one application first, run tests and a production build with budgets, fix breaking changes reported by the schematics, then lint. Deploy that application to a preview URL and run smoke tests there. Shared libraries and the remaining applications follow after those checks. The example budgets set `initial` to 1mb for warnings and 2mb for errors. `anyComponentStyle` uses 10kb for warnings and 30kb for errors.

The release also adds official LLM prompts, an Angular CLI MCP server and agent skills. The article recommends using the official Angular documentation and angular.dev/ai as agent references. Generated diffs still need review because agents can mix signal and RxJS patterns in one file.

Teams on v21 can adopt v22 now when they need stable Signal Forms or Angular Aria. A near-term upgrade also makes sense for hydration performance and long-term support. Teams in the middle of a release, or dependent on libraries without v22 peer support, can wait for one sprint. The recommended approach keeps working forms and effects in place, adopts stable APIs in new code and revisits hot paths when they are changed.