Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 8, 2025

This PR contains the following updates:

Package Change Age Confidence
zone.js (source, changelog) 0.15.1 -> 0.16.0 age confidence

Warning

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


Release Notes

angular/angular (zone.js)

v0.16.0

Compare Source

BREAKING CHANGE
  • IE/Non-Chromium Edge are not supported anymore.

Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (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.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 8, 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: ui/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: @angular/[email protected]
npm error Found: [email protected]
npm error node_modules/zone.js
npm error   zone.js@"0.16.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional zone.js@"~0.15.0" from @angular/[email protected]
npm error node_modules/@angular/core
npm error   @angular/core@"20.3.15" from the root project
npm error   peerOptional @angular/core@"^20.0.0" from @angular-devkit/[email protected]
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"20.3.12" from the root project
npm error   7 more (@angular/build, @angular/animations, @angular/common, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/zone.js
npm error   peerOptional zone.js@"~0.15.0" from @angular/[email protected]
npm error   node_modules/@angular/core
npm error     @angular/core@"20.3.15" from the root project
npm error     peerOptional @angular/core@"^20.0.0" from @angular-devkit/[email protected]
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"20.3.12" from the root project
npm error     7 more (@angular/build, @angular/animations, @angular/common, ...)
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/2025-12-08T02_52_12_548Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-08T02_52_12_548Z-debug-0.log

@renovate renovate bot requested a review from a team as a code owner December 8, 2025 02:52
@renovate renovate bot requested a review from r-tome December 8, 2025 02:52
@bitwarden-bot bitwarden-bot changed the title [deps]: Update zone.js to v0.16.0 [PM-29392] [deps]: Update zone.js to v0.16.0 Dec 8, 2025
@bitwarden-bot
Copy link

Internal tracking:

@renovate renovate bot changed the title [PM-29392] [deps]: Update zone.js to v0.16.0 [deps]: Update zone.js to v0.16.0 Dec 8, 2025
@vincentsalucci vincentsalucci requested review from eliykat and removed request for r-tome December 8, 2025 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants