@angular/core@22.1.3
Review before merging.
Release notes list 1 breaking change: Event handler attributes are no longer allowed in Meta elements, which may break existing code.
Why this verdict
- Release notes list 1 breaking change: Event handler attributes are no longer allowed in Meta elements, which may break existing code.Evidence
Confidence 100% · algorithm v1 · computed 2026-11-22. How verdicts work
Supply chain and security
- Malware reports
- None known (OSV)
- Known advisories
- None known (OSV)
- License
- MIT
- Install scripts
- None
- Build provenance
- No provenance
- Weekly downloads
- 37,475
Compatibility
No compatibility boundary is crossed: this is a patch or minor release on a stable major.
Breaking changes in the release notes
- Event handler attributes are no longer allowed in Meta elements, which may break existing code.“disallow event handler attributes in Meta”
AI-extracted from the official release notes and checked against the quoted text. Read the source
5 issues mention this version in angular/angular within 14 days of release. See them on GitHub
Check the official release notes below for behaviour changes before merging.
Release notes
Read the Angular changelog on Changes.Watch or the package page on npm for this version’s features and fixes.
New in this release
- Object.hasOwn is now used to detect object trigger values.“detect object trigger values with Object.hasOwn common”
- KeyValuePipe.transform now preserves literal key unions.“preserve literal key union in KeyValuePipe.transform()”
- &ngsp; is preserved between sibling control‑flow blocks.“preserve &ngsp; between sibling control flow blocks”
- setClassMetadata decorators now accept readonly arrays.“accept readonly arrays for setClassMetadata decorators”
- RawScopeInfoFromDecorator now allows readonly arrays.“allow readonly arrays in RawScopeInfoFromDecorator”
- A debuggableFn is exposed for non‑computed signal graph nodes.“expose debuggableFn for non computed signal graph nodes”
- A descriptive error is thrown when a hydration node is missing.“throw a descriptive error instead of crashing when a hydration node is missing”
- NG0500 is thrown instead of a raw TypeError on element hydration mismatches.“throw NG0500 instead of a raw TypeError on element hydration mismatch”
AI-extracted from the official release notes and checked against the quoted text. Read the source
Deprecations and deadlines
The maintainer has not deprecated this version on npm.
Did upgrading to 22.1.3 work for you?
Results appear once three developers have voted.