fix(deps): update dependency @angular/compiler to v20 [security]

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@angular/compiler (source)	~18.2.0 → ~20.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Angular: Template and Attribute Namespace Sanitization Bypass (XSS)

CVE-2026-50557 / GHSA-f3m7-gqxr-g87x

More information

Details

An issue in the @angular/compiler and @angular/core packages allows bypassing element and attribute sanitization/validation through specific namespace workarounds.

Specifically, namespaced script elements (e.g., <svg:script> or <:svg:script>) were not properly identified as script elements by the Angular template preparser, allowing them to pass through template compilation without being stripped.

Furthermore, security context schema mappings for element attributes did not consistently handle attributes within namespaced elements (like SVG and MathML), opening up gaps where malicious namespaced attributes could bypass runtime and compile-time sanitizers.

Combined, these flaws enable an attacker who can inject or supply a template/tag structure with custom namespaces to bypass Angular's script-stripping logic and attribute sanitizers, leading to client-side Cross-Site Scripting (XSS).

Impact

Any Angular application that compiles user-controlled templates at runtime, or relies on sanitization of namespaced elements/attributes, is vulnerable to this security bypass.

Once exploited, this allows a malicious actor to inject a namespaced script element or dynamic attribute bindings, bypassing core sanitization constraints to execute arbitrary JavaScript within the target user's browser context. This could lead to session hijacking, sensitive data exposure, or unauthorized actions on behalf of the user.

Attack Preconditions

To successfully exploit these vulnerabilities, the following environment parameters and application states must all concurrently exist:

1. User-Controlled Template Input: The application must accept user-controlled inputs that are directly processed by the Angular template compiler at runtime.
2. Namespace Parsing Support: The input structure must employ custom namespace prefixes (such as <svg:script>) to evade standard tag-name blocklists/checks.
3. Absence of Additional Context Sanitization: The application does not perform separate input sanitization before feeding values to the Angular compiler.

Patches

• 22.0.0-rc.2
• 21.2.15
• 20.3.22
• 19.2.23

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/angular/angular/security/advisories/GHSA-f3m7-gqxr-g87x
• https://nvd.nist.gov/vuln/detail/CVE-2026-50557
• https://github.com/angular/angular/pull/68689
• https://github.com/angular/angular/pull/68868
• https://github.com/angular/angular

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Angular vulnerable to XSS in i18n attribute bindings

CVE-2026-32635 / GHSA-g93w-mfhg-p222

More information

Details

A Cross-Site Scripting (XSS) vulnerability has been identified in the Angular runtime and compiler. It occurs when the application uses a security-sensitive attribute (for example href on an anchor tag) together with Angular's ability to internationalize attributes. Enabling internationalization for the sensitive attribute by adding i18n-<attribute> name bypasses Angular's built-in sanitization mechanism, which when combined with a data binding to untrusted user-generated data can allow an attacker to inject a malicious script.

The following example illustrates the issue:

<a href="" i18n-href>Click me</a>

The following attributes have been confirmed to be vulnerable:

• action
• background
• cite
• codebase
• data
• formaction
• href
• itemtype
• longdesc
• poster
• src
• xlink:href

Impact

When exploited, this vulnerability allows an attacker to execute arbitrary code within the context of the vulnerable application's domain. This enables:

• Session Hijacking: Stealing session cookies and authentication tokens.
• Data Exfiltration: Capturing and transmitting sensitive user data.
• Unauthorized Actions: Performing actions on behalf of the user.

Attack Preconditions

1. The application must use a vulnerable version of Angular.
2. The application must bind unsanitized user input to one of the attributes mentioned above.
3. The bound value must be marked for internationalization via the presence of a i18n-<name> attribute on the same element.

Patches

• 22.0.0-next.3
• 21.2.4
• 20.3.18
• 19.2.20

Workarounds

The primary workaround is to ensure that any data bound to the vulnerable attributes is never sourced from untrusted user input (e.g., database, API response, URL parameters) until the patch is applied, or when it is, it shouldn't be marked for internationalization.

Alternatively, users can explicitly sanitize their attributes by passing them through Angular's DomSanitizer:

import {Component, inject, SecurityContext} from '@angular/core';
import {DomSanitizer} from '@angular/platform-browser';

@Component({
  template: `
    <form action="" i18n-action>
      <button>Submit</button>
    </form>
  `,
})
export class App {
  url: string;

  constructor() {
    const dangerousUrl = 'javascript:alert(1)';
    const sanitizer = inject(DomSanitizer);
    this.url = sanitizer.sanitize(SecurityContext.URL, dangerousUrl) || '';
  }
}

References

• Fix 1
• Fix 2

Severity

• CVSS Score: 8.6 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

References

• https://github.com/angular/angular/security/advisories/GHSA-g93w-mfhg-p222
• https://nvd.nist.gov/vuln/detail/CVE-2026-32635
• https://github.com/angular/angular/pull/67541
• https://github.com/angular/angular/pull/67561
• https://github.com/angular/angular/commit/224e60ecb1b90115baa702f1c06edc1d64d86187
• https://github.com/angular/angular/commit/78dea55351fb305b33a919c43a6b363137eca166
• https://github.com/angular/angular/commit/8630319f74c9575a21693d875cc7d5252516146d
• https://github.com/angular/angular/commit/ed2d324f9cc12aab6cfa0569ef10b73243a62c65
• https://github.com/angular/angular

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

@​angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS)

CVE-2026-54265 / GHSA-58w9-8g37-x9v5

More information

Details

An issue in the @angular/compiler package allows bypassing DOM property sanitization through the use of two-way property bindings.

Specifically, when a native DOM property that requires sanitization (such as innerHTML, srcdoc, src, href, data, or sandbox) is bound using the two-way binding syntax (e.g., [(innerHTML)]="value" or bindon-innerHTML="value"), the Angular template compiler failed to apply the appropriate schema-derived sanitizer resolution to the TwoWayProperty operation. As a result, native two-way DOM bindings were emitted without the required sanitizer function, whereas equivalent one-way bindings would be properly sanitized.

This flaw enables an attacker who can control the value of a two-way bound sensitive property to bypass Angular's built-in sanitization logic, potentially leading to client-side Cross-Site Scripting (XSS).

Impact

Any Angular application that uses two-way data binding ([()] or bindon-) on security-sensitive native DOM properties (like innerHTML, href on <a>, src on <img>/<iframe>, etc.) is vulnerable to this security bypass.

Once exploited, this allows a malicious actor to supply an unsanitized property binding value that bypasses core sanitization constraints. This could lead to the execution of arbitrary JavaScript within the target user's browser context, potentially resulting in session hijacking, sensitive data exposure, or unauthorized actions on behalf of the user.

Attack Preconditions

To successfully exploit this vulnerability, the following environment parameters and application states must concurrently exist:

1. Two-Way Binding on Sensitive Properties: The application must bind to a sensitive native DOM property using the two-way binding syntax (e.g., <div [(innerHTML)]="userContent"></div>).
2. User-Controlled Input: The value bound to this property must be influenceable by user-controlled input.
3. Absence of Additional Sanitization: The application does not perform separate manual sanitization (e.g., via DomSanitizer) before passing the value to the bound property.

Patches

• 22.0.1
• 21.2.17
• 20.3.25

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/angular/angular/security/advisories/GHSA-58w9-8g37-x9v5
• https://nvd.nist.gov/vuln/detail/CVE-2026-54265
• https://github.com/angular/angular/pull/69107
• https://github.com/angular/angular/commit/3c70270c96677c0dd33585f2afe8e187113e5fb4
• https://github.com/angular/angular

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes

CVE-2026-69151 / GHSA-jj27-h5hq-8x99

More information

Details

A Cross-Site Scripting (XSS) vulnerability has been identified in the Angular compiler's internationalization (i18n) pipeline. Although Angular disallows binding to event-handler attributes such as onclick and onerror through standard attribute validation (validateAttribute() / validateProperty()), the i18n metadata collection path allowed these same attribute names to be marked for translation using i18n-on* attributes (e.g., i18n-onerror).

When exploited, a lower-trust translation file could replace a benign static handler such as onerror="void 0" with arbitrary executable JavaScript in the localized build.

The following example illustrates a vulnerable pattern:

<img src="foo.jpg" onerror="void 0" i18n-onerror />

Impact

When exploited, this vulnerability allows arbitrary JavaScript execution within the context of the vulnerable application's domain if an attacker can control or influence the translation files used during localization. This can lead to:

• Session Hijacking: Accessing session cookies, tokens, or sensitive user data.
• Unauthorized Actions: Performing actions on behalf of the authenticated user.

Patched Versions

• 22.0.1
• 21.2.19
• 20.3.27

Workarounds

Ensure that static event-handler attributes (e.g., onerror, onclick) are never marked for internationalization (i18n-on*) in application templates, and ensure translation files are sourced from trusted origins.

Severity

• CVSS Score: 7.6 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/angular/angular/security/advisories/GHSA-jj27-h5hq-8x99
• https://github.com/angular/angular/pull/68821
• https://github.com/angular/angular/pull/69306
• https://github.com/angular/angular/commit/417a4071a776464d549509ed3aec121dbd2fda5e
• https://github.com/angular/angular/commit/6c41f5ca01c0ae045fc7d929b72853a11eb55865
• https://github.com/angular/angular

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

angular/angular (@​angular/compiler)

v20.0.0

Compare Source

Blog post: https://blog.angular.dev/announcing-angular-v20-b5c9c06cf301

Breaking Changes

common

• Using the Y formatter (week-numbering year) without also including w (week number) is now detected as suspicious date pattern, as y is typically intended.
• AsyncPipe now directly catches unhandled errors in
  subscriptions and promises and reports them to the application's
  ErrorHandler. For Zone-based applications, these errors would have
  been caught by ZoneJS and reported to ErrorHandler so the result is
  generally the same. The change to the exact mechanism for reporting can
  result in differences in test environments that will require test
  updates.

compiler

• 'in' in an expression now refers to the operator

• void in an expression now refers to the operator

  Previously an expression in the template like {{void}} referred to a
  property on the component class. After this change it now refers to the
  void operator, which would make the above example invalid. If you have
  existing expressions that need to refer to a property named void,
  change the expression to use this.void instead: {{this.void}}.

• Parenthesis are always respected.

  This can lead to runtime breakages when a nullish coalescing operator is nested within parentheses.
  eg. {{ (foo?.bar).baz }} will throw if foo is nullish. This is the same behavior as native JavaScript.

core

• TypeScript versions less than 5.8 are no longer supported.

• the TestBed.flushEffects() was removed - use
  the TestBed.tick() instead.

• provideExperimentalCheckNoChangesForDebug has several
  breaking changes:

  • It is renamed to provideCheckNoChangesConfig
  • The behavior applies to all checkNoChanges runs
  • The useNgZoneOnStable option is removed. This wasn't found to be generally
    more useful than interval

• provideExperimentalZonelessChangeDetection is
  renamed to provideZonelessChangeDetection as it is now "Developer
  Preview" rather than "Experimental".

• • InjectFlags has been removed.
  • inject no longer accepts InjectFlags.
  • Injector.get no longer accepts InjectFlags.
  • EnvironmentInjector.get no longer accepts InjectFlags.
  • TestBed.get no longer accepts InjectFlags.
  • TestBed.inject no longer accepts InjectFlags.
• • TestBed.get has been removed. Use TestBed.inject instead.

• afterRender was renamed to afterEveryRender.

• • Angular no longer supports Node.js v18.
  • Node.js versions 22.0 to 22.10 are also no longer supported.

  Before upgrading to Angular v20, ensure the Node.js version is at least 20.11.1.
  For the full list of supported versions, visit: https://angular.dev/reference/versions

• PendingTasks.run no longer returns the result of the
  async function. If this behavior is desired, it can be re-implemented
  manually with the PendingTasks.add. Be aware, however, that promise rejections
  will need to be handled or they can cause the node process to shut down
  when using SSR.

• Uncaught errors in listeners which were previously only reported to
  ErrorHandler are now also reported to Angular's internal error
  handling machinery. For tests, this means that the error will be
  rethrown by default rather than only logging the error. Developers
  should fix these errors, catch them in the test if the test is
  intentionally covering an error case, or use rethrowApplicationErrors: false in configureTestingModule as a last resort.

• The any overload has been removed from
  injector.get. It now only supports ProviderToken<T> and (deprecated
  since v4) string.

• Animations are guaranteed to be flushed when Angular
  runs automatic change detection or manual calls to ApplicationRef.tick.
  Prior to this change, animations would not be flushed in some situations
  if change detection did not run on any views attached to the
  application. This change can affect tests which may rely on the old
  behavior, often by making assertions on DOM elements that should have
  been removed but weren't because DOM removal is delayed until animations
  are flushed.

• ApplicationRef.tick will no longer catch and report
  errors to the application ErrorHandler. Errors will instead be thrown out of
  the method and will allow callers to determine how to handle these
  errors, such as aborting follow-up work or reporting the error and
  continuing.

• This commit deprecates ng-reflect-* attributes and updates the runtime to stop producing them by default. Please refactor application and test code to avoid relying on ng-reflect-* attributes.

  To enable a more seamless upgrade to v20, we've added the provideNgReflectAttributes() function (can be imported from the @angular/core package), which enables the mode in which Angular would be producing those attribites (in dev mode only). You can add the provideNgReflectAttributes() function to the list of providers within the bootstrap call.

router

• The RedirectFn can now return Observable or
  Promise. Any code that directly calls functions returning this type
  may need to be adjusted to account for this.
• Several methods in the public API of the Router which
  required writable arrays have now been updated to accept readonly
  arrays when no mutations are done.
• The guards arrays on Route no longer include any in
  the type union. The union includes functions for the functional guards
  as well as a type matching Injector.get: ProviderToken<T>|string.
  Note that string is still deprecated on both the route guards and
  Injector.get.

Deprecations

core

• ngIf/ngFor/ngSwitch are deprecated. Use the control flow blocks instead (@for/@if/@switch).

platform-browser

• All entries of the @angular/platform-browser-dynamic
• HammerJS support is deprecated and will be removed in a future major version.

platform-server

• @angular/platform-server/testing

  Use e2e tests to verify SSR behavior instead.

common

Commit	Type	Description
2e5362a469	feat	accept undefined inputs in NgTemplateOutlet (#​61404)
b7d3f3dbfc	feat	Allow passing ScrollOptions to ViewportScroller (#​61002)
74cceba587	feat	throw error for suspicious date patterns (#​59798)
255c79e048	fix	cleanup updateLatestValue if view is destroyed before promise resolves (#​58041)
739cadae62	fix	Handle errors in async pipe subscriptions (#​60057)
cbbea70fa3	fix	issue a warning instead of an error when NgOptimizedImage exceeds the preload limit (#​60879)
fc4a56d5c5	fix	rename httpResource function in factory (#​60022)
785a1110e6	fix	resolve host binding type issues (#​60481)

compiler

Commit	Type	Description
7a971766dc	feat	add extended diagnostic for uninvoked track function on @for blocks (#​60495)
f2d5cf7edd	feat	support exponentiation operator in templates (#​59894)
51b8ff23ce	feat	support tagged template literals in expressions (#​59947)
1b8e7ab9fe	feat	support the in keyword in Binary expression (#​58432)
0361c2d81f	feat	support void operator in templates (#​59894)
8b990a31c3	fix	error if rawText isn't estimated correctly (#​60529)
4fe489f1b4	fix	exponentiation should be right-to-left associative (#​60101)
ef1fd137a9	fix	incorrect spans for template literals (#​60323)
e0d378d20e	fix	incorrectly handling let declarations inside i18n (#​60512)
b70ad3c4e6	fix	proper handling of typeof, void in RecursiveAstVisitor (#​60101)
e25e6c95a2	fix	remove TypeScript from linker (#​61635)
768239a89c	perf	reduce allocations for let declarations only used in the same view (#​60512)

compiler-cli

Commit	Type	Description
bec1610da2	feat	add extended diagnostic for invalid nullish coalescing (#​60279)
c889382a20	feat	detect missing structural directive imports (#​59443)
1971e57a45	feat	support type checking of host bindings (#​60267)
9ec9c7e1b8	fix	avoid fatal diagnostics for invalid module schemas (#​61220)
a1cacc5b17	fix	avoid fatal diagnostics for missing template files (#​58673)
1e6faad479	fix	correctly parse event name in HostListener (#​60561)
ffb19e64f1	fix	preserve required parens for nullish coalescing (#​60060)
7c9b4892e9	fix	preserve required parens in exponentiation expressions (#​60101)
7e03af898e	fix	set correct target when type checking events (#​60561)
2d51a203dc	fix	wrong event name for host listener decorators (#​60460)

core

Commit	Type	Description
22d3f0562c	feat	add hook for producer creation side effects (#​60333)
fe57332fc5	feat	add input binding support to dynamically-created components (#​60137)
65adb3024d	feat	Add provider which reports unhandled errors on window to ErrorHandler (#​60704)
b154fb3911	feat	add support for two-way bindings on dynamically-created components (#​60342)
82aa2c1a52	feat	add the ability to apply directives to dynamically-created components (#​60137)
326d48afb4	feat	drop support for TypeScript older than 5.8 (#​60197)
d260ca3091	feat	emit template function for template related profiler hooks (#​60174)
a4bad8d361	feat	export signalGetFn from signal primitives (#​60497)
4812215a7b	feat	Expose Injector.destroy on Injector created with Injector.create (#​60054)
c1bcae91dd	feat	expose performance data in Chrome DevTools (#​60789)
809b5b4596	feat	introduce new DI profiling event (#​60158)
d5fd7349fb	feat	introduce TestBed.tick() (#​60993)
4e88e18a8e	feat	mark toObservable as stable (#​60449)
727cda3856	feat	mark linkedSignal API as public (#​60865)
644d9f3bbd	feat	mark the toSignal API as stable (#​60442)
e711f99d81	feat	move provideExperimentalCheckNoChangesForDebug to provideCheckNoChangesConfig (#​60906)
7ccec1494f	feat	move DOCUMENT token into core (#​60663)
953c4b2580	feat	Move zoneless change detection to dev preview (#​60748)
611baaf069	feat	remove InjectFlags from public API (#​60318)
5e209cb560	feat	remove TestBed.get (#​60414)
d8fbb909ce	feat	rename afterRender to afterEveryRender and stabilize (#​60999)
567522398f	feat	stabilize incremental hydration api (#​60888)
8d050b5bfc	feat	stabilize linkedSignal API (#​60741)
866cea9a05	feat	Stabilize PendingTasks Injectable (#​60716)
bf8492b871	feat	stabilize withI18nSupport() api (#​60889)
be44cc8f40	feat	support listening to outputs on dynamically-created components (#​60137)
fe9b79b615	feat	update Node.js version support (#​60545)
e170d24240	fix	add migration away from InjectFlags (#​60318)
7eb59d3887	fix	added @​angular/compiler as a peer dependency (#​55610)
7232ce5b17	fix	Catch and report rejections in async function of PendingTasks.run (#​60044)
fd12220a35	fix	defer block render failures should report to application error handler (#​60149)
3459faadbf	fix	do not allow setInput to be used with inputBinding (#​60137)
0ac949c266	fix	do not run change detection on global error events (#​60944)
4fe34f4cfe	fix	enable stashing only when withEventReplay() is invoked (#​61077)
962b59b14e	fix	Ensure ComponentFixture does not duplicate error reporting from FakeAsync (#​60104)
7b819be83f	fix	Ensure errors in listeners report to the application error handler (#​60251)
ff772d7800	fix	fix typing on injector.get to omit 'any' (#​60202)
13d1c8ab38	fix	fixes timing of hydration cleanup on control flow (#​60425)
0b69b61929	fix	Flush animations when no component has been checked (#​58089)
3ba39bc28f	fix	getting resource value throws an error instead of returning undefined (#​61441)
ca6295e90b	fix	handle different DI token types in Chrome DevTools integration (#​61333)
0162ceb427	fix	inject migration should treat @Attribute as optional (#​60916)
ea5eb28865	fix	input targeting not checking if input exists on host (#​60137)
c8951159ac	fix	mark zone.js as an optional peer dependency (#​61616)
d62379bb13	fix	move reload method from Resource to WritableResource (#​61441)
a89f1cff24	fix	narrow error type for resources API (#​61441)
624be2ef0c	fix	prevent stash listener conflicts (#​59635)
017cc0a37c	fix	properly handle app stabilization with defer blocks (#​61040)
6e79eaf739	fix	reading resource value after reload in the error state (#​61441)
3d85d9363c	fix	reduce total memory usage of various migration schematics (#​60774)
1c7b356625	fix	release hasPendingTasks observers (#​59723)
43cbc58254	fix	remove forceRoot flag for effects (#​60535)
48974c3cf8	fix	remove rejectErrors option encourages uncaught exceptions (#​60397)
491b0a4ead	fix	Remove duplicate reporting of errors in CDR.detectChanges (#​60056)
04d963c0a5	fix	remove unused parameter from listener instruction (#​60406)
0ae1889560	fix	run ApplicationRef.prototype.bootstrap in NgZone (#​60720)
a611b234d7	fix	run root effects in creation order (#​60534)
338818ce89	fix	Surface errors from ApplicationRef.tick to callsite (#​60102)
350776b412	fix	TestBed.tick should ensure test components are synchronized (#​61382)
3d4ddd2247	fix	Testing should not throw when Zone does not patch test FW APIs (#​61628)
30e081287d	fix	update min Node.js support to 20.19, 22.12, and 24.0 (#​61500)
b407157ee8	refactor	Deprecate the structural directives ngIf/ngFor/ngSwitch. (#​60492)
c2987d8402	refactor	stop producing ng-reflect attributes by default (#​60973)

forms

Commit	Type	Description
a07ee60989	feat	add markAllAsDirty to AbstractControl (#​58663)
bdfbd54932	feat	Allow to reset a form without emitting events (#​60354)
81fe0536fd	fix	Make sure statusChanges is emitted (#​57098)
bdd5e20423	fix	resolve host binding type issues (#​60481)

http

Commit	Type	Description
ccc5cc068f	feat	add keepalive support for fetch requests (#​60621)
5795e03cdf	fix	Delay stabilization until next app synchronization (#​60656)

platform-browser

Commit	Type	Description
bc2cab747f	refactor	Deprecate the platform-browser-dynamic package (#​61043)
a980ac9a6a	refactor	Deprecate the HammerJS integration (#​60257)

platform-server

Commit	Type	Description
2240a21c97	refactor	deprecate the testing entry point (#​60915)

router

Commit	Type	Description
0bb4bd661e	feat	Add ability to directly abort a navigation (#​60380)
62de7d930a	feat	add asynchronous redirects (#​60863)
7c12cb1df9	feat	Allow resolvers to read resolved data from ancestors (#​59860)
ff98ccb193	feat	support custom elements for RouterLink (#​60290)
219f41d049	fix	Prevent dangling promise rejections from internal navigations (#​60162)
2419060fef	fix	relax required types on router commands to readonly array (#​60345)
c57951d58f	fix	Remove 'any' type from route guards (#​60378)
db2f2d99c8	fix	Scroller should scroll as soon as change detection completes (#​60086)

v19.2.25

Compare Source

platform-server

Commit	Type	Description
e2fb854d55	fix	throw on suspicious URLs and restrict protocol-relative URLs
0a8befb493	fix	update domino to latest version

v19.2.24

Compare Source

compiler

| Commit | Type | Description

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular/compiler-cli@18.2.7
npm error Found: @angular/compiler@20.0.7
npm error node_modules/@angular/compiler
npm error   @angular/compiler@"~20.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/compiler@"18.2.7" from @angular/compiler-cli@18.2.7
npm error node_modules/@angular/compiler-cli
npm error   dev @angular/compiler-cli@"~18.2.0" from the root project
npm error   peer @angular/compiler-cli@"^18.0.0" from @angular-devkit/build-angular@18.2.7
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"~18.2.0" from the root project
npm error     3 more (@nx/angular, @storybook/angular, jest-preset-angular)
npm error   4 more (@angular/build, @ngtools/webpack, @storybook/angular, jest-preset-angular)
npm error
npm error Conflicting peer dependency: @angular/compiler@18.2.7
npm error node_modules/@angular/compiler
npm error   peer @angular/compiler@"18.2.7" from @angular/compiler-cli@18.2.7
npm error   node_modules/@angular/compiler-cli
npm error     dev @angular/compiler-cli@"~18.2.0" from the root project
npm error     peer @angular/compiler-cli@"^18.0.0" from @angular-devkit/build-angular@18.2.7
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"~18.2.0" from the root project
npm error       3 more (@nx/angular, @storybook/angular, jest-preset-angular)
npm error     4 more (@angular/build, @ngtools/webpack, @storybook/angular, jest-preset-angular)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-07-30T17_39_50_950Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-30T17_39_50_950Z-debug-0.log