Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Aug 30, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular-devkit/build-angular ~0.1102.4~0.1102.19 age adoption passing confidence
@angular/cli 11.2.1411.2.19 age adoption passing confidence

Release Notes

angular/angular-cli (@​angular/cli)

v11.2.19

Compare Source

@​angular-devkit/architect-cli
Commit Type Description
75caa1143 fix update minimist to 1.2.6
@​angular-devkit/schematics-cli
Commit Type Description
80d479e9f fix update minimist to 1.2.6
@​angular-devkit/benchmark
Commit Type Description
f61cd1a79 fix update minimist to 1.2.6

Special Thanks

Alan Agius and Doug Parker

v11.2.18

Compare Source

@​angular-devkit/build-angular
Commit Type Description
534678450 fix updated webpack-dev-server to latest security patch

Special Thanks

Doug Parker and iRealNirmal

v11.2.17

Compare Source

@​angular/cli
Commit Type Description
1efff8f82 fix exclude deprecated packages with removal migration from update

Special Thanks

Alan Agius and Doug Parker

v11.2.16

Compare Source

@​angular/cli
Commit Type Description
f456b0962 fix error when updating Angular packages across multi-major migrations
886d2511e fix logic which determines which temp version of the CLI is to be download during ng update
776d1210a fix update ng update output for Angular packages

Special Thanks

Alan Agius and Doug Parker

v11.2.15

Compare Source

Commits

@​angular-devkit/build-angular (0.1102.15)

Commit Description Notes
update `critters` to version `0.0.12` [Closes #​20794]

Special Thanks

Joey Perrott, Alan Agius


Configuration

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

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate
Copy link
Author

renovate bot commented Aug 30, 2021

⚠ 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: frontend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/compiler
npm ERR!   dev @angular/compiler@"~11.2.0" from the root project
npm ERR!   peer @angular/compiler@">= 11.2.0 < 12.0.0" from @angular-eslint/[email protected]
npm ERR!   node_modules/@angular-eslint/eslint-plugin
npm ERR!     dev @angular-eslint/eslint-plugin@"2.0.2" from the root project
npm ERR!   4 more (@angular-eslint/eslint-plugin-template, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @angular-devkit/build-angular@"~0.1102.19" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/compiler
npm ERR!   peer @angular/compiler@"11.2.14" from @angular/[email protected]
npm ERR!   node_modules/@angular/compiler-cli
npm ERR!     dev @angular/compiler-cli@"~11.2.0" from the root project
npm ERR!     peer @angular/compiler-cli@"^11.0.0 || ^11.2.0-next" from @angular-devkit/[email protected]
npm ERR!     node_modules/@angular-devkit/build-angular
npm ERR!       dev @angular-devkit/build-angular@"~0.1102.19" from the root project
npm ERR!     2 more (@angular/localize, ng-packagr)
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/renovate-cache/others/npm/_logs/2022-11-20T13_32_16_078Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-20T13_32_16_078Z-debug-0.log

@renovate renovate bot force-pushed the renovate/angular-cli-monorepo branch 2 times, most recently from 3bbc963 to f7c41ad Compare September 7, 2021 08:41
@renovate renovate bot force-pushed the renovate/angular-cli-monorepo branch from f7c41ad to 8d31b05 Compare September 19, 2021 07:16
@renovate renovate bot force-pushed the renovate/angular-cli-monorepo branch from 8d31b05 to 20bd02a Compare October 27, 2021 20:54
@renovate renovate bot changed the title chore: update dependency @angular-devkit/build-angular to ~0.1102.14 chore: update angular-cli monorepo Oct 27, 2021
@renovate renovate bot force-pushed the renovate/angular-cli-monorepo branch 2 times, most recently from f5014b4 to 7494e48 Compare February 28, 2022 09:19
@renovate renovate bot force-pushed the renovate/angular-cli-monorepo branch from 7494e48 to 0ba1f4b Compare March 31, 2022 03:12
@renovate renovate bot force-pushed the renovate/angular-cli-monorepo branch from 0ba1f4b to 685f518 Compare September 25, 2022 14:46
@renovate renovate bot force-pushed the renovate/angular-cli-monorepo branch from 685f518 to 2199665 Compare November 20, 2022 13:32
@renovate
Copy link
Author

renovate bot commented Aug 10, 2025

⚠️ 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: frontend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: @angular/[email protected]
npm error node_modules/@angular/compiler
npm error   dev @angular/compiler@"~11.2.0" from the root project
npm error   peer @angular/compiler@">= 11.2.0 < 12.0.0" from @angular-eslint/[email protected]
npm error   node_modules/@angular-eslint/eslint-plugin
npm error     dev @angular-eslint/eslint-plugin@"2.0.2" from the root project
npm error   4 more (@angular-eslint/eslint-plugin-template, ...)
npm error
npm error Could not resolve dependency:
npm error dev @angular-devkit/build-angular@"~0.1102.19" from the root project
npm error
npm error Conflicting peer dependency: @angular/[email protected]
npm error node_modules/@angular/compiler
npm error   peer @angular/compiler@"11.2.14" from @angular/[email protected]
npm error   node_modules/@angular/compiler-cli
npm error     dev @angular/compiler-cli@"~11.2.0" from the root project
npm error     peer @angular/compiler-cli@"^11.0.0 || ^11.2.0-next" from @angular-devkit/[email protected]
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"~0.1102.19" from the root project
npm error     2 more (@angular/localize, ng-packagr)
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-01-08T20_28_10_036Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-08T20_28_10_036Z-debug-0.log

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant