New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open

renovate wants to merge 1 commit into master from renovate/npm-@angular/core-vulnerability

renovate bot commented Jun 18, 2022 •

edited

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@angular/core (source)	`~8.0.0` -> `~10.2.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`

`v9.1.9`

`v9.1.8`

`v9.1.7`

`v9.1.6`

`v9.1.5`

`v9.1.4`

`v9.1.3`

`v9.1.2`

`v9.1.1`

`v9.1.0`

`v9.0.7`

`v9.0.6`

`v9.0.5`

`v9.0.4`

`v9.0.3`

`v9.0.2`

`v9.0.1`

`v9.0.0`

`v8.2.14`

`v8.2.13`

`v8.2.12`

`v8.2.11`

`v8.2.10`

`v8.2.9`

`v8.2.8`

`v8.2.7`

`v8.2.6`

`v8.2.5`

`v8.2.4`

`v8.2.3`

`v8.2.2`

`v8.2.1`

`v8.2.0`

`v8.1.3`

`v8.1.2`

`v8.1.1`

`v8.1.0`

`v8.0.3`

`v8.0.2`

`v8.0.1`

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 has been generated by Mend Renovate. View repository job log here.

renovate bot changed the title ~~chore(deps): update dependency @angular/core to 11.0.5 [security]~~ fix(deps): update dependency @angular/core to v11 [security]


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

cd3341c

renovate bot force-pushed the renovate/npm-@angular/core-vulnerability branch from 3dbf27e to cd3341c Compare

October 11, 2023 04:58

renovate bot changed the title ~~fix(deps): update dependency @angular/core to v11 [security]~~ fix(deps): update dependency @angular/core to v10 [security]

Author

renovate bot commented Oct 11, 2023

⚠ 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 WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: spur-template-for-angular@0.0.0
npm ERR! Found: rxjs@6.4.0
npm ERR! node_modules/rxjs
npm ERR!   rxjs@"~6.4.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^6.5.3" from @angular/core@10.2.5
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"~10.2.0" from the root project
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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/4fca4c/9fe46c/cache/others/npm/_logs/2023-10-11T04_58_24_473Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/4fca4c/9fe46c/cache/others/npm/_logs/2023-10-11T04_58_24_473Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment