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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update angular monorepo #53

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

fix(deps): update angular monorepo #53

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 7, 2020 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular/animations (source) 9.1.9 -> 9.1.13 age adoption passing confidence
@angular/common (source) 9.1.9 -> 9.1.13 age adoption passing confidence
@angular/compiler (source) 9.1.9 -> 9.1.13 age adoption passing confidence
@angular/compiler-cli (source) 9.1.9 -> 9.1.13 age adoption passing confidence
@angular/core (source) 9.1.9 -> 9.1.13 age adoption passing confidence
@angular/forms (source) 9.1.9 -> 9.1.13 age adoption passing confidence
@angular/language-service (source) 9.0.4 -> 9.1.13 age adoption passing confidence
@angular/platform-browser (source) 9.1.9 -> 9.1.13 age adoption passing confidence
@angular/platform-browser-dynamic (source) 9.1.9 -> 9.1.13 age adoption passing confidence
@angular/router (source) 9.1.9 -> 9.1.13 age adoption passing confidence
zone.js (source, changelog) ~0.10.2 -> ~0.14.0 age adoption passing confidence

Release Notes

angular/angular (@​angular/animations)

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

angular/angular (@​angular/common)

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

angular/angular (@​angular/compiler)

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

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

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

angular/angular (@​angular/core)

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

angular/angular (@​angular/forms)

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

angular/angular (@​angular/language-service)

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

v9.1.9

Compare Source

v9.1.8

Compare Source

v9.1.7

Compare Source

v9.1.6

Compare Source

v9.1.5

Compare Source

v9.1.4

Compare Source

v9.1.3

Compare Source

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.7

Compare Source

v9.0.6

Compare Source

v9.0.5

Compare Source

angular/angular (@​angular/platform-browser)

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

angular/angular (@​angular/platform-browser-dynamic)

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

angular/angular (@​angular/router)

v9.1.13

Compare Source

v9.1.12

Compare Source

v9.1.11

Compare Source

v9.1.10

Compare Source

angular/angular (zone.js)

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

v0.13.3

Compare Source

Bug Fixes

v0.13.2

Compare Source

Bug Fixes

v0.13.1

Compare Source

Bug Fixes
Features
Reverts

v0.13.0

Compare Source

v0.12.0

Compare Source

Bug Fixes

0.11.8 (2022-08-08)

Features
  • zone.js: Update to the simpler Async Stack Tagging v2 API (#​46958) (f23232f)

0.11.7 (2022-07-20)

Bug Fixes
  • zone.js: do not invoke jasmine done callback multiple times with waitForAsync (4e77c7fbf38)
Features
  • zone.js: add AsyncStackTaggingZoneSpec implementation (#​46693) (848a009)
  • zone.js: include jasmine describe block name when raising unexpected task error (de86285)
  • zone.js: include zone name when sync-test zone reports tasks (72c2567)

0.11.6 (2022-06-02)

Bug Fixes
BREAKING CHANGES
  • zone.js: in TaskTrackingZoneSpec track a periodic task until it is cancelled

The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking. If you used TaskTrackingZoneSpec and
checked the pending macroTasks e.g. using (this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask'), then
its behavior slightly changed for periodic macrotasks. For example,
previously the setInterval macrotask was no longer tracked after its
callback was executed for the first time. Now it's tracked until
the task is explicitly cancelled, e.g with clearInterval(id).

0.11.5 (2022-03-03)

Bug Fixes
Features

0.11.4 (2021-02-10)

Bug Fixes
Features

0.11.3 (2020-10-27)

Bug Fixes

0.11.2 (2020-09-19)

Bug Fixes
Features
Refactor
  • zone.js: refactor(zone.js): rename several internal apis in fake async zone spec (#​39127) (8a68669)
Build
  • zone.js: build(zone.js): zone.js should output esm format for fesm2015 bundles (#​39203) (822b838)
BREAKING CHANGES
  • zone.js: ZoneJS no longer swallows errors produced by Object.defineProperty calls.

Prior to this change, ZoneJS monkey patched Object.defineProperty and if there is an error
(such as the property is not configurable or not writable) the patched logic swallowed it
and only console.log was produced. This behavior used to hide real errors,
so the logic is now updated to trigger original errors (if any). One exception
where the patch remains in place is document.registerElement
(to allow smooth transition for code/polyfills that rely on old behavior in legacy browsers).
If your code relies on the old behavior (where errors were not thrown before),
you may need to update the logic to handle the errors that are no longer masked by ZoneJS patch.

0.11.1 (2020-08-19)

Bug Fixes

v0.11.8

Compare Source

Features
  • zone.js: Update to the simpler Async Stack Tagging v2 API (#​46958) (f23232f)

v0.11.7

Compare Source

Bug Fixes
  • zone.js: do not invoke jasmine done callback multiple times with waitForAsync (4e77c7fbf38)
Features
  • zone.js: add AsyncStackTaggingZoneSpec implementation (#​46693) (848a009)
  • zone.js: include jasmine describe block name when raising unexpected task error (de86285)
  • zone.js: include zone name when sync-test zone reports tasks (72c2567)

v0.11.6

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: in TaskTrackingZoneSpec track a periodic task until it is cancelled

The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking. If you used TaskTrackingZoneSpec and
checked the pending macroTasks e.g. using (this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask'), then
its behavior slightly changed for periodic macrotasks. For example,
previously the setInterval macrotask was no longer tracked after its
callback was executed for the first time. Now it's tracked until
the task is explicitly cancelled, e.g with clearInterval(id).

v0.11.5

Compare Source

Bug Fixes
Features

v0.11.4

Compare Source

Bug Fixes
Features

v0.11.3

Compare Source

Bug Fixes

v0.11.2

Bug Fixes
Features
Refactor
  • zone.js: refactor(zone.js): rename several internal apis in fake async zone spec (#​39127) (8a68669)
Build
  • zone.js: build(zone.js): zone.js should output esm format for fesm2015 bundles (#​39203) (822b838)
BREAKING CHANGES
  • zone.js: ZoneJS no longer swallows errors produced by Object.defineProperty calls.

Prior to this change, ZoneJS monkey patched Object.defineProperty and if there is an error
(such as the property is not configurable or not writable) the patched logic swallowed it
and only console.log was produced. This behavior used to hide real errors,
so the logic is now updated to trigger original errors (if any). One exception
where the patch remains in place is document.registerElement
(to allow smooth transition for code/polyfills that rely on old behavior in legacy browsers).
If your code relies on the old behavior (where errors were not thrown before),
you may need to update the logic to handle the errors that are no longer masked by ZoneJS patch.

v0.11.1

Prior to v0.11.1, Zone.js provided two distribution bundle formats in the dist folder.
They were (1) ES5 bundle distributed as zone.js and (2) ES2015 bundle distributed as zone-evergreen.js.
These bundles are used for Angular's differential-loading mechanism.

Prior to v0.11.11 the following code

import 'zone.js';

would load the ES5 bundle from dist/zone.js.

Starting with v0.11.1, Zone.js follows the Angular Package Format, so the folder structure of the Zone.js bundles is updated to match Angular Package Format.
So the same code

import 'zone.js';

now loads the ES2015 bundle instead.

This is a breaking change for legacy browsers such as IE11.

For backwards compatibility zone.js continues to distribute the same bundles under dist.
To restore the old behavior change the polyfills.ts generated by Angular CLI to import like so:

import 'zone.js/dist/zone';

v0.11.0

Compare Source

Bug Fixes

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.

👻 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/angular-monorepo branch 3 times, most recently from 75262a8 to b76519e Compare December 17, 2020 03:16
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from b76519e to 9fac700 Compare February 16, 2021 19:42
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 2 times, most recently from 3bcdf8e to ab725df Compare May 15, 2021 19:37
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from ab725df to f3740d2 Compare March 7, 2022 11:08
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from f3740d2 to 132b39c Compare June 18, 2022 22:35
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from ff21568 to 0cc51d3 Compare March 11, 2023 03:52
@renovate renovate bot changed the title Update angular monorepo chore(deps): update angular monorepo Mar 11, 2023
@renovate
Copy link
Author

renovate bot commented Mar 11, 2023 •
edited

⚠ 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: @ngrx/core@1.2.0
npm ERR! Found: rxjs@6.5.4
npm ERR! node_modules/rxjs
npm ERR!   rxjs@"6.5.4" from the root project
npm ERR!   rxjs@"6.5.4" from @angular-devkit/schematics@9.1.7
npm ERR!   node_modules/@angular-devkit/schematics
npm ERR!     @angular-devkit/schematics@"9.1.7" from @angular/cli@9.1.7
npm ERR!     node_modules/@angular/cli
npm ERR!       dev @angular/cli@"^9.0.4" from the root project
npm ERR!     @angular-devkit/schematics@"9.1.7" from @schematics/angular@9.1.7
npm ERR!     node_modules/@schematics/angular
npm ERR!       @schematics/angular@"9.1.7" from @angular/cli@9.1.7
npm ERR!       node_modules/@angular/cli
npm ERR!         dev @angular/cli@"^9.0.4" from the root project
npm ERR!     1 more (@schematics/update)
npm ERR!   20 more (@angular-devkit/core, @angular-devkit/architect, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^5.0.0-beta.12" from @ngrx/core@1.2.0
npm ERR! node_modules/@ngrx/core
npm ERR!   @ngrx/core@"^1.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: rxjs@5.5.12
npm ERR! node_modules/rxjs
npm ERR!   peer rxjs@"^5.0.0-beta.12" from @ngrx/core@1.2.0
npm ERR!   node_modules/@ngrx/core
npm ERR!     @ngrx/core@"^1.2.0" from the root project
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-04-30T22_13_05_807Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update angular monorepo fix(deps): update angular monorepo Mar 15, 2023
@renovate Renovate
Copy link
Author

renovate bot commented May 17, 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: @ngrx/core@1.2.0
npm ERR! Found: rxjs@6.5.4
npm ERR! node_modules/rxjs
npm ERR!   rxjs@"6.5.4" from the root project
npm ERR!   rxjs@"6.5.4" from @angular-devkit/schematics@9.1.7
npm ERR!   node_modules/@angular-devkit/schematics
npm ERR!     @angular-devkit/schematics@"9.1.7" from @angular/cli@9.1.7
npm ERR!     node_modules/@angular/cli
npm ERR!       dev @angular/cli@"^9.0.4" from the root project
npm ERR!     @angular-devkit/schematics@"9.1.7" from @schematics/angular@9.1.7
npm ERR!     node_modules/@schematics/angular
npm ERR!       @schematics/angular@"9.1.7" from @angular/cli@9.1.7
npm ERR!       node_modules/@angular/cli
npm ERR!         dev @angular/cli@"^9.0.4" from the root project
npm ERR!     1 more (@schematics/update)
npm ERR!   20 more (@angular-devkit/core, @angular-devkit/architect, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^5.0.0-beta.12" from @ngrx/core@1.2.0
npm ERR! node_modules/@ngrx/core
npm ERR!   @ngrx/core@"^1.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: rxjs@5.5.12
npm ERR! node_modules/rxjs
npm ERR!   peer rxjs@"^5.0.0-beta.12" from @ngrx/core@1.2.0
npm ERR!   node_modules/@ngrx/core
npm ERR!     @ngrx/core@"^1.2.0" from the root project
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-17T06_10_47_996Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants