Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 10, 2024

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
zone.js (source, changelog) ^0.10.3^0.16.0 age confidence

Release Notes

angular/angular (zone.js)

v0.16.0

Compare Source

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

v0.15.1

Compare Source

Bug Fixes

v0.15.0

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: fakeAsync will now flush pending timers at the end of
    the given function by default. To opt-out of this, you can use {flush: false} in options parameter of fakeAsync

0.14.10 (2024-08-05)

Features
  • zone.js: Add 'flush' parameter option to fakeAsync to flush after the test (#​57137) (99d679d)

0.14.8 (2024-07-17)

Bug Fixes

0.14.7 (2024-06-06)

Bug Fixes

0.14.6 (2024-05-16)

Bug Fixes

0.14.5 (2024-04-30)

Bug Fixes

0.14.4 (2024-02-13)

Bug Fixes

0.14.3 (2023-12-19)

Bug Fixes
Features

0.14.2 (2023-11-03)

Bug Fixes
  • zone.js: disable wrapping unhandled promise error by default (6d7eb35)

14.0.1 (2023-10-25)

Bug Fixes

v0.14.10

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: fakeAsync will now flush pending timers at the end of
    the given function by default. To opt-out of this, you can use {flush: false} in options parameter of fakeAsync

0.14.10 (2024-08-05)

Features
  • zone.js: Add 'flush' parameter option to fakeAsync to flush after the test (#​57137) (99d679d)

0.14.8 (2024-07-17)

Bug Fixes

0.14.7 (2024-06-06)

Bug Fixes

0.14.6 (2024-05-16)

Bug Fixes

0.14.5 (2024-04-30)

Bug Fixes

0.14.4 (2024-02-13)

Bug Fixes

0.14.3 (2023-12-19)

Bug Fixes
Features

0.14.2 (2023-11-03)

Bug Fixes
  • zone.js: disable wrapping unhandled promise error by default (6d7eb35)

14.0.1 (2023-10-25)

Bug Fixes

v0.14.8

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: fakeAsync will now flush pending timers at the end of
    the given function by default. To opt-out of this, you can use {flush: false} in options parameter of fakeAsync

0.14.10 (2024-08-05)

Features
  • zone.js: Add 'flush' parameter option to fakeAsync to flush after the test (#​57137) (99d679d)

0.14.8 (2024-07-17)

Bug Fixes

0.14.7 (2024-06-06)

Bug Fixes

0.14.6 (2024-05-16)

Bug Fixes

0.14.5 (2024-04-30)

Bug Fixes

0.14.4 (2024-02-13)

Bug Fixes

0.14.3 (2023-12-19)

Bug Fixes
Features

0.14.2 (2023-11-03)

Bug Fixes
  • zone.js: disable wrapping unhandled promise error by default (6d7eb35)

14.0.1 (2023-10-25)

Bug Fixes

v0.14.7

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: fakeAsync will now flush pending timers at the end of
    the given function by default. To opt-out of this, you can use {flush: false} in options parameter of fakeAsync

0.14.10 (2024-08-05)

Features
  • zone.js: Add 'flush' parameter option to fakeAsync to flush after the test (#​57137) (99d679d)

0.14.8 (2024-07-17)

Bug Fixes

0.14.7 (2024-06-06)

Bug Fixes

0.14.6 (2024-05-16)

Bug Fixes

0.14.5 (2024-04-30)

Bug Fixes

0.14.4 (2024-02-13)

Bug Fixes

0.14.3 (2023-12-19)

Bug Fixes
Features

0.14.2 (2023-11-03)

Bug Fixes
  • zone.js: disable wrapping unhandled promise error by default (6d7eb35)

14.0.1 (2023-10-25)

Bug Fixes

v0.14.6

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: fakeAsync will now flush pending timers at the end of
    the given function by default. To opt-out of this, you can use {flush: false} in options parameter of fakeAsync

0.14.10 (2024-08-05)

Features
  • zone.js: Add 'flush' parameter option to fakeAsync to flush after the test (#​57137) (99d679d)

0.14.8 (2024-07-17)

Bug Fixes

0.14.7 (2024-06-06)

Bug Fixes

0.14.6 (2024-05-16)

Bug Fixes

0.14.5 (2024-04-30)

Bug Fixes

0.14.4 (2024-02-13)

Bug Fixes

0.14.3 (2023-12-19)

Bug Fixes
Features

0.14.2 (2023-11-03)

Bug Fixes
  • zone.js: disable wrapping unhandled promise error by default (6d7eb35)

14.0.1 (2023-10-25)

Bug Fixes

v0.14.5

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: fakeAsync will now flush pending timers at the end of
    the given function by default. To opt-out of this, you can use {flush: false} in options parameter of fakeAsync

0.14.10 (2024-08-05)

Features
  • zone.js: Add 'flush' parameter option to fakeAsync to flush after the test (#​57137) (99d679d)

0.14.8 (2024-07-17)

Bug Fixes

0.14.7 (2024-06-06)

Bug Fixes

0.14.6 (2024-05-16)

Bug Fixes

0.14.5 (2024-04-30)

Bug Fixes

0.14.4 (2024-02-13)

Bug Fixes

0.14.3 (2023-12-19)

Bug Fixes
Features

0.14.2 (2023-11-03)

Bug Fixes
  • zone.js: disable wrapping unhandled promise error by default (6d7eb35)

14.0.1 (2023-10-25)

Bug Fixes

v0.14.4

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: fakeAsync will now flush pending timers at the end of
    the given function by default. To opt-out of this, you can use {flush: false} in options parameter of fakeAsync

0.14.10 (2024-08-05)

Features
  • zone.js: Add 'flush' parameter option to fakeAsync to flush after the test (#​57137) (99d679d)

0.14.8 (2024-07-17)

Bug Fixes

0.14.7 (2024-06-06)

Bug Fixes
  • zone.js: do not mutate event listener options (may be readonly) (#​55796) (85c1719), closes #​54142
  • zone.js: store remove

Configuration

📅 Schedule: 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 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 Feb 10, 2024

⚠ 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/core@9.1.1
npm ERR! Found: zone.js@0.14.3
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"^0.14.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.10.3" from @angular/core@9.1.1
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"^9.1.0" from the root project
npm ERR!   peer @angular/core@"9.1.1" from @angular/animations@9.1.1
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"^9.1.0" from the root project
npm ERR!     1 more (@angular/platform-browser)
npm ERR!   11 more (@angular/common, @angular/forms, ...)
npm ERR! 
npm ERR! Conflicting peer dependency: zone.js@0.10.3
npm ERR! node_modules/zone.js
npm ERR!   peer zone.js@"~0.10.3" from @angular/core@9.1.1
npm ERR!   node_modules/@angular/core
npm ERR!     @angular/core@"^9.1.0" from the root project
npm ERR!     peer @angular/core@"9.1.1" from @angular/animations@9.1.1
npm ERR!     node_modules/@angular/animations
npm ERR!       @angular/animations@"^9.1.0" from the root project
npm ERR!       1 more (@angular/platform-browser)
npm ERR!     11 more (@angular/common, @angular/forms, ...)
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/2024-02-10T10_02_51_599Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-02-10T10_02_51_599Z-debug-0.log

@vercel
Copy link

vercel bot commented Feb 10, 2024

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
outlet Error Error Nov 20, 2025 1:34am

@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 4e4d756 to 059a67b Compare August 21, 2024 21:31
@renovate renovate bot changed the title fix(deps): update dependency zone.js to ^0.14.0 fix(deps): update dependency zone.js to ^0.15.0 Aug 21, 2024
@renovate
Copy link
Contributor Author

renovate bot commented Aug 21, 2024

⚠️ 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 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/core@9.1.1
npm error Found: zone.js@0.16.0
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 peer zone.js@"~0.10.3" from @angular/core@9.1.1
npm error node_modules/@angular/core
npm error   @angular/core@"^9.1.0" from the root project
npm error   peer @angular/core@"9.1.1" from @angular/animations@9.1.1
npm error   node_modules/@angular/animations
npm error     @angular/animations@"^9.1.0" from the root project
npm error     1 more (@angular/platform-browser)
npm error   11 more (@angular/common, @angular/forms, ...)
npm error
npm error Conflicting peer dependency: zone.js@0.10.3
npm error node_modules/zone.js
npm error   peer zone.js@"~0.10.3" from @angular/core@9.1.1
npm error   node_modules/@angular/core
npm error     @angular/core@"^9.1.0" from the root project
npm error     peer @angular/core@"9.1.1" from @angular/animations@9.1.1
npm error     node_modules/@angular/animations
npm error       @angular/animations@"^9.1.0" from the root project
npm error       1 more (@angular/platform-browser)
npm error     11 more (@angular/common, @angular/forms, ...)
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-08T16_28_16_033Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-08T16_28_16_033Z-debug-0.log

@dmnktoe dmnktoe removed their assignment Jun 13, 2025
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 059a67b to 7c08825 Compare July 3, 2025 01:18
@coderabbitai
Copy link

coderabbitai bot commented Jul 3, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 7c08825 to 0e3bd08 Compare November 20, 2025 01:33
@renovate renovate bot changed the title fix(deps): update dependency zone.js to ^0.15.0 fix(deps): update dependency zone.js to ^0.16.0 Nov 20, 2025
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.

2 participants