@angular/core@21.2.19
Review before merging.
Release notes list 3 breaking changes: Disallows i18n event attributes, which may break existing templates using them.
Why this verdict
- Release notes list 3 breaking changes: Disallows i18n event attributes, which may break existing templates using them.Evidence
- 1 known advisory (worst: moderate), fixed in 21.2.20.Evidence
Confidence 100% · algorithm v1 · computed 2026-11-22. How verdicts work
Supply chain and security
- Malware reports
- None known (OSV)
- Known advisories
- 1 known
- License
- MIT
- Install scripts
- None
- Build provenance
- No provenance
- Weekly downloads
- 74,548
- GHSA-hh8m-fm6v-7cvgAngular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
Compatibility
No compatibility boundary is crossed: this is a patch or minor release on a stable major.
Breaking changes in the release notes
- Disallows i18n event attributes, which may break existing templates using them.“disallow i18n event attributes”
- Restricts event handler checks to property names longer than two characters, potentially breaking short handler names.“restrict possible event handler check to property names longer than 2 characters”
- Enables XSRF protection for root‑provided HttpClient on the platform server, changing default behavior.“enable xsrf for root provided HttpClient platform server”
AI-extracted from the official release notes and checked against the quoted text. Read the source
1 issue mentions 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
- Adds distinction for repeated transfer cache parameters.“distinguish repeated transfer cache params”
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 21.2.19 work for you?
Results appear once three developers have voted.