Angular 22.1.3

Angular 22.1.3 landed on August 19, 2026, and before you get excited about new framework magic, let's be clear about what this actually is: a patch release. That means bug fixes, not a shiny new feature launch. And that's a good thing to know before you assume the upgrade is risk-free.

The Routine Bug-Squashing

The core team spent this patch tightening up internals rather than adding surface area. A few of the more notable fixes:

• Signals — stop running further effects once one destroys the view mid-flush, and expose a debuggable function for non-computed signal graph nodes. If you've been chasing a weird signal-related crash, this is likely the fix.
• Hydration — instead of crashing with a raw TypeError when a hydration node is missing on element mismatch, Angular now throws a descriptive error (NG0500). That is the kind of change that saves you an hour of header-scratching in dev.
• HTTP — oversized fetch response bodies are now cancelled, which should help with runaway memory on large payloads.
• Forms — forbidden two-way bindings on FormField are now reported, and dev mode warns when ngModel cannot reach its parent NgForm across a component boundary.
• Router — fixed canDeactivate receiving the wrong component for named outlets in componentless parent routes.

The Less-Glamorous Under-the-Hood Changes

There's also a housekeeping theme here: multiple commits replace hand-rolled hasOwnProperty calls with Object.hasOwn, and both setClassMetadata and RawScopeInfoFromDecorator now accept readonly arrays. The compiler also preserves &ngsp; space between sibling control-flow blocks, and the language server recovers projects for external templates in solution-style workspaces.

These are the changes that never make the keynote slides but genuinely reduce sharp edges.

Should You Upgrade?

It's a patch — the upgrade path is short. But as ever with Angular patches, don't click through blindly. Pull it into a branch, run your test suite, and specifically re-check anything touching signals, hydration, or forms, since those carried the bulk of the fixes. If your app is healthy on 22.1.x, this is a low-risk bump. If it's already showing hydration warnings, this one deserves your attention.

Angular 22.1.3 is available now via the Angular CLI (ng update). Upgrade deliberately, not on autopilot.