Skip to content
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.

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

Update dependency zone.js to ~0.15.0 #131

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 8, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
zone.js (source, changelog) ~0.13.0 -> ~0.15.0 age adoption passing confidence

Release Notes

angular/angular (zone.js)

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

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

v0.14.8

Compare Source

Bug Fixes

v0.14.7

Compare Source

Bug Fixes

v0.14.6

Compare Source

Bug Fixes

v0.14.5

Compare Source

Bug Fixes

v0.14.4

Compare Source

Bug Fixes

v0.14.3

Compare Source

Bug Fixes
Features

v0.14.2

Compare Source

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

v0.14.1

Compare Source

v0.14.0

Compare Source

Features
BREAKING CHANGES
  • zone.js: Deep and legacy dist/ imports like zone.js/bundles/zone-testing.js and zone.js/dist/zone are no longer allowed. zone-testing-bundle and zone-testing-node-bundle are also no longer part of the package.

The proper way to import zone.js and zone.js/testing is:

import 'zone.js';
import 'zone.js/testing';

0.13.3 (2023-09-12)

Bug Fixes

0.13.2 (2023-09-07)

Bug Fixes

v0.13.1 (2023-06-09)

Bug Fixes
Features
Reverts

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 Oct 8, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular/[email protected]
npm ERR! Found: [email protected]
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.11.4 || ~0.12.0 || ~0.13.0" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"^15.1.3" from the root project
npm ERR!   peer @angular/core@"15.2.10" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"^15.1.3" from the root project
npm ERR!     2 more (@angular/platform-browser, ngx-bootstrap)
npm ERR!   9 more (@angular/common, @angular/compiler, @angular/forms, ...)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   peer zone.js@"~0.11.4 || ~0.12.0 || ~0.13.0" from @angular/[email protected]
npm ERR!   node_modules/@angular/core
npm ERR!     @angular/core@"^15.1.3" from the root project
npm ERR!     peer @angular/core@"15.2.10" from @angular/[email protected]
npm ERR!     node_modules/@angular/animations
npm ERR!       @angular/animations@"^15.1.3" from the root project
npm ERR!       2 more (@angular/platform-browser, ngx-bootstrap)
npm ERR!     9 more (@angular/common, @angular/compiler, @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/worker/6ab186/0f52cc/cache/others/npm/_logs/2023-10-08T17_02_54_120Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/6ab186/0f52cc/cache/others/npm/_logs/2023-10-08T17_02_54_120Z-debug-0.log

@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 6f34013 to 74cafd1 Compare August 21, 2024 20:32
@renovate renovate bot changed the title Update dependency zone.js to ~0.14.0 Update dependency zone.js to ~0.15.0 Aug 21, 2024
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 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.15.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer zone.js@"~0.13.0" from @angular/[email protected]
npm error node_modules/@angular/core
npm error   @angular/core@"^16.2.12" from the root project
npm error   peer @angular/core@"16.2.12" from @angular/[email protected]
npm error   node_modules/@angular/animations
npm error     @angular/animations@"^16.2.12" from the root project
npm error     2 more (@angular/platform-browser, ngx-bootstrap)
npm error   9 more (@angular/common, @angular/compiler, @angular/forms, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/zone.js
npm error   peer zone.js@"~0.13.0" from @angular/[email protected]
npm error   node_modules/@angular/core
npm error     @angular/core@"^16.2.12" from the root project
npm error     peer @angular/core@"16.2.12" from @angular/[email protected]
npm error     node_modules/@angular/animations
npm error       @angular/animations@"^16.2.12" from the root project
npm error       2 more (@angular/platform-browser, ngx-bootstrap)
npm error     9 more (@angular/common, @angular/compiler, @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 /tmp/renovate/cache/others/npm/_logs/2024-08-21T20_32_21_273Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-08-21T20_32_21_273Z-debug-0.log

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.

0 participants