digital-bank-ui
digital-bank-ui copied to clipboard

Published 20 hours ago •

Reame
Issues

fix(deps): update dependency @angular/core to v10 [security]

Open renovate[bot] opened this issue 3 months ago • 1 comments

This PR contains the following updates:

Package	Change	Age	Confidence
@angular/core (source)	`^9.0.4` -> `^10.0.0`

GitHub Vulnerability Alerts

CVE-2021-4231

A vulnerability was found in Angular up to 11.0.4/11.1.0-next.2. It has been classified as problematic. Affected is the handling of comments. The manipulation leads to cross site scripting. It is possible to launch the attack remotely but it might require an authentication first. Upgrading to version 10.2.5, 11.0.5 or 11.1.0-next.3 is advised to to address this issue.

Release Notes

angular/angular (@angular/core)

`v10.2.5`

`v10.2.4`

`v10.2.3`

`v10.2.2`

`v10.2.1`

`v10.2.0`

`v10.1.6`

`v10.1.5`

`v10.1.4`

`v10.1.3`

`v10.1.2`

`v10.1.1`

`v10.1.0`

`v10.0.14`

`v10.0.13`

`v10.0.12`

`v10.0.11`

`v10.0.10`

`v10.0.9`

`v10.0.8`

`v10.0.7`

`v10.0.6`

`v10.0.5`

`v10.0.4`

`v10.0.3`

`v10.0.2`

`v10.0.1`

`v10.0.0`

`v9.1.13`

`v9.1.12`

`v9.1.11`

`v9.1.10`

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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.

Aug 13 '25 16:08 renovate[bot]

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular/[email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"^10.0.0" from the root project
npm ERR!   peer @angular/core@">= 6.0.0" from @akveo/[email protected]
npm ERR!   node_modules/@akveo/ng2-completer
npm ERR!     @akveo/ng2-completer@"^9.0.1" from the root project
npm ERR!     peer @akveo/ng2-completer@"9.0.1" from [email protected]
npm ERR!     node_modules/ng2-smart-table
npm ERR!       ng2-smart-table@"^1.6.0" from the root project
npm ERR!   7 more (@angular/cdk, @angular/material, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"9.1.9" from @angular/[email protected]
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"^9.0.4" from the root project
npm ERR!   peer @angular/animations@"^9.0.0 || ^10.0.0-0" from @angular/[email protected]
npm ERR!   node_modules/@angular/material
npm ERR!     @angular/material@"^9.2.4" from the root project
npm ERR!     1 more (@covalent/core)
npm ERR!   3 more (@angular/platform-browser, @nebular/theme, @swimlane/ngx-charts)
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"9.1.9" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"^9.0.4" from the root project
npm ERR!     peer @angular/animations@"^9.0.0 || ^10.0.0-0" from @angular/[email protected]
npm ERR!     node_modules/@angular/material
npm ERR!       @angular/material@"^9.2.4" from the root project
npm ERR!       1 more (@covalent/core)
npm ERR!     3 more (@angular/platform-browser, @nebular/theme, @swimlane/ngx-charts)
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-11-18T23_57_02_313Z-debug-0.log

Aug 13 '25 16:08 renovate[bot]