Closed renovate[bot] closed 2 years ago
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:
The artifact failure details are included below:
real 0m7.360s
user 0m6.453s
sys 0m0.729s
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @angular-devkit/build-angular@13.2.2
npm ERR! Found: typescript@4.6.3
npm ERR! node_modules/typescript
npm ERR! typescript@"4.6.3" from the root project
npm ERR! peer typescript@">=4.4.2 <4.7" from @angular/compiler-cli@13.3.11
npm ERR! node_modules/@angular/compiler-cli
npm ERR! dev @angular/compiler-cli@"13.3.11" from the root project
npm ERR! peer @angular/compiler-cli@"^13.0.0" from @angular-devkit/build-angular@13.2.2
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"^13.2.2" from the root project
npm ERR! 1 more (@ngtools/webpack)
npm ERR! 3 more (ts-node, tslint, tsutils)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=4.4.3 <4.6" from @angular-devkit/build-angular@13.2.2
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"^13.2.2" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: typescript@4.5.5
npm ERR! node_modules/typescript
npm ERR! peer typescript@">=4.4.3 <4.6" from @angular-devkit/build-angular@13.2.2
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"^13.2.2" 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/2022-06-19T01_01_43_085Z-debug-0.log
This PR contains the following updates:
0.11.5
->0.11.6
Release Notes
angular/angular
### [`v0.11.6`](https://togithub.com/angular/angular/blob/HEAD/packages/zone.js/CHANGELOG.md#0116-httpsgithubcomangularangularcomparezonejs-0115zonejs-0116-2022-06-02) [Compare Source](https://togithub.com/angular/angular/compare/zone.js-0.11.5...zone.js-0.11.6) ##### Bug Fixes - **zone.js:** check if `process` is defined when patching the `GlobalErrors.install` ([#45392](https://togithub.com/angular/angular/issues/45392)) ([c7bcc1b](https://togithub.com/angular/angular/commit/c7bcc1b50182e5378756aa4528a24075b5be026e)), closes [#42260](https://togithub.com/angular/angular/issues/42260) - **zone.js:** in TaskTrackingZoneSpec track a periodic task until it is cancelled ([#45391](https://togithub.com/angular/angular/issues/45391)) ([f19b36f](https://togithub.com/angular/angular/commit/f19b36f462803b3b3b9410391c039649541b10bc)) - **zone.js:** read `Symbol.species` safely ([#45369](https://togithub.com/angular/angular/issues/45369)) ([e2eaac3](https://togithub.com/angular/angular/commit/e2eaac34b06a558145be41853f1d3585c1108880)) - **zone.js:** should ignore multiple resolve call ([#45283](https://togithub.com/angular/angular/issues/45283)) ([aebf165](https://togithub.com/angular/angular/commit/aebf165359ad6de5a8bacd9cb91651fc4175aaad)), closes [#44913](https://togithub.com/angular/angular/issues/44913) - **zone.js:** swallow the error when the element callback is not patchable ([#45400](https://togithub.com/angular/angular/issues/45400)) ([4ea70e3](https://togithub.com/angular/angular/commit/4ea70e36b998208302183f78088637f3de86323d)), closes [lwc/engine-core/src/framework/base-bridge-element.ts#L180-L186](https://togithub.com/lwc/engine-core/src/framework/base-bridge-element.ts/issues/L180-L186) [#42546](https://togithub.com/angular/angular/issues/42546) ##### 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)`.Configuration
📅 Schedule: Branch creation - "after 8am and before 5pm on saturday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.