POC icon indicating copy to clipboard operation
POC copied to clipboard

Published 20 hours ago • verified publisher icon rajadilipkolli

fix(deps): update dependency zone.js to v0.15.0

Open renovate[bot] opened this issue 1 year ago • 3 comments

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
zone.js (source, changelog) 0.13.3 -> 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 - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

Summary by CodeRabbit

  • New Features

    • Upgraded the zone.js library to version 0.15.0, enhancing performance and potentially introducing new features and bug fixes for improved asynchronous operations and change detection in the application.

  • Bug Fixes

    • The update may resolve existing issues related to asynchronous execution contexts, improving overall application stability.

renovate[bot] avatar Nov 23 '23 14:11 renovate[bot]

⚠ 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/blog-angular-ui/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.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.13.0" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"16.2.12" from the root project
npm ERR!   peer @angular/core@"16.2.12" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"16.2.12" from the root project
npm ERR!     1 more (@angular/platform-browser)
npm ERR!   6 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.13.0" from @angular/[email protected]
npm ERR!   node_modules/@angular/core
npm ERR!     @angular/core@"16.2.12" from the root project
npm ERR!     peer @angular/core@"16.2.12" from @angular/[email protected]
npm ERR!     node_modules/@angular/animations
npm ERR!       @angular/animations@"16.2.12" from the root project
npm ERR!       1 more (@angular/platform-browser)
npm ERR!     6 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

renovate[bot] avatar Nov 23 '23 14:11 renovate[bot]

[!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.

Walkthrough

The update to the frontend/blog-angular-ui project involves upgrading the zone.js dependency from version 0.13.3 to 0.15.0. This change reflects the project's effort to utilize the latest versions of critical libraries that facilitate change detection and asynchronous operations in Angular applications.

Changes

Files Change Summary
frontend/blog-angular-ui/package.json Updated zone.js from 0.13.3 to 0.15.0

Poem

🐰 In the garden where code does bloom,
A leap in zone.js brings joy, not gloom.
From 0.13 to 15, what a grand sight,
Performance and fixes dance in the light.
With hops and skips, let the changes ring,
For tech and bunnies, it’s a wondrous thing! 🌼

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

coderabbitai[bot] avatar Mar 16 '24 03:03 coderabbitai[bot]

⚠️ 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/blog-angular-ui/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.15.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.13.0" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"16.2.12" from the root project
npm ERR!   peer @angular/core@"16.2.12" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"16.2.12" from the root project
npm ERR!     1 more (@angular/platform-browser)
npm ERR!   6 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.13.0" from @angular/[email protected]
npm ERR!   node_modules/@angular/core
npm ERR!     @angular/core@"16.2.12" from the root project
npm ERR!     peer @angular/core@"16.2.12" from @angular/[email protected]
npm ERR!     node_modules/@angular/animations
npm ERR!       @angular/animations@"16.2.12" from the root project
npm ERR!       1 more (@angular/platform-browser)
npm ERR!     6 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

renovate[bot] avatar May 11 '24 05:05 renovate[bot]