Angular 22.1.1

Angular 22.1.1 is out, and before anyone starts planning a party, let's be clear about what this is: a patch release. Six fixes, zero new features. That's it. And that's fine — patch releases exist to close the cracks, not to sell you something.

What Actually Changed

The core team split their attention between two areas this time: the runtime and the HTTP layer. Both sets of changes read like housekeeping, but housekeeping has a way of biting you if you ignore it long enough.

Core Fixes Worth Knowing

• Hydration triggers initialize after late runtime activation — if your app lazily activates parts of the runtime, hydration events were firing before everything was fully ready. That ordering bug is now closed.
• Invalid style property bindings now warn — Angular will start complaining when a style binding receives a value it can't render. If your templates pass numbers where strings belong, you'll hear about it in the console.

HTTP Layer Cleanup

• No more aborted-request aborts — FetchBackend was cancelling requests that had already completed. Wasted work, now avoided.
• Charset-aware decoding — the fetch backend's text decoder now respects the Content-Type charset instead of guessing.
• Root interceptors in the terminal chain — interceptors attached at the root now execute in the final request chain as intended.
• Cookie parsing hardened — RFC 6265 DQUOTE characters are stripped, and a URIError in parseCookieValue is handled instead of crashing the request.

The Skeptic's Bottom Line

Nothing here will break your app — patch releases don't work that way. The style-binding warning is the only change that could surface new console noise after an upgrade, and it's a warning, not an error. Update when your CI window allows it, run your test suite, and move on. The genuinely interesting stuff is sitting in 22.2.0-next.