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

fix(deps): update angular monorepo #32

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 21, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular/animations (source) 13.3.11 -> 13.4.0 age adoption passing confidence
@angular/common (source) 13.3.11 -> 13.4.0 age adoption passing confidence
@angular/compiler (source) 13.3.11 -> 13.4.0 age adoption passing confidence
@angular/compiler-cli (source) 13.3.11 -> 13.4.0 age adoption passing confidence
@angular/core (source) 13.3.11 -> 13.4.0 age adoption passing confidence
@angular/elements (source) 13.3.11 -> 13.4.0 age adoption passing confidence
@angular/forms (source) 13.3.11 -> 13.4.0 age adoption passing confidence
@angular/platform-browser (source) 13.3.11 -> 13.4.0 age adoption passing confidence
@angular/platform-browser-dynamic (source) 13.3.11 -> 13.4.0 age adoption passing confidence
@angular/router (source) 13.3.11 -> 13.4.0 age adoption passing confidence
zone.js (source, changelog) 0.11.6 -> 0.14.7 age adoption passing confidence

Release Notes

angular/angular (@​angular/animations)

v13.4.0

Compare Source

common
Commit Type Description
ae34dbca1b feat Backport NgOptimizedImage to v13

Special Thanks

Alex Castle and Paul Gschwendtner

v13.3.12

Compare Source

Breaking Changes

core
  • Existing iframe usages may have security-sensitive attributes applied as an attribute or property binding in a template or via host bindings in a directive. Such usages would require an update to ensure compliance with the new stricter rules around iframe bindings.
core
Commit Type Description
b1d7b79ff4 fix hardening attribute and property binding rules for <iframe> elements (#​48029)

Special Thanks

Andrew Kushnir, Andrew Scott, George Looshch, Joey Perrott and Paul Gschwendtner

angular/angular (zone.js)

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

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)

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
Copy link
Contributor Author

renovate bot commented Jul 21, 2022

⚠ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: torrow-widget@1.0.0
npm ERR! Found: zone.js@0.14.5
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.11.4" from @angular/core@13.4.0
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"13.4.0" from the root project
npm ERR!   peer @angular/core@"13.4.0" from @angular/animations@13.4.0
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"13.4.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-30T21_28_04_752Z-debug-0.log

@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 8d2f6f1 to d103717 Compare August 12, 2022 15:41
@renovate renovate bot changed the title fix(deps): update dependency zone.js to v0.11.7 fix(deps): update dependency zone.js to v0.11.8 Aug 12, 2022
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from d103717 to 8203bdd Compare November 20, 2022 16:14
@renovate renovate bot changed the title fix(deps): update dependency zone.js to v0.11.8 fix(deps): update dependency zone.js to v0.12.0 Nov 20, 2022
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 8203bdd to c07fe7f Compare November 21, 2022 21:31
@renovate renovate bot changed the title fix(deps): update dependency zone.js to v0.12.0 fix(deps): update angular monorepo Nov 21, 2022
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from c07fe7f to 5de0705 Compare March 18, 2023 21:57
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 5de0705 to 94ee456 Compare April 17, 2023 10:09
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 94ee456 to 7559267 Compare June 12, 2023 16:20
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 3 times, most recently from 7534ca7 to d94e2cd Compare September 18, 2023 11:40
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from d94e2cd to be6583d Compare October 26, 2023 16:49
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from be6583d to a768da4 Compare November 3, 2023 19:43
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from a768da4 to a44520d Compare January 9, 2024 18:24
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from a44520d to f6377a8 Compare February 13, 2024 21:36
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from f6377a8 to 2981c18 Compare April 30, 2024 21:28
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 2981c18 to ccfdcb9 Compare May 17, 2024 05:33
Copy link
Contributor 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: torrow-widget@1.0.0
npm ERR! Found: zone.js@0.14.7
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"0.14.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.11.4" from @angular/core@13.4.0
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"13.4.0" from the root project
npm ERR!   peer @angular/core@"13.4.0" from @angular/animations@13.4.0
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"13.4.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-06-06T22_52_28_416Z-debug-0.log

@renovate renovate bot force-pushed the renovate/angular-monorepo branch from ccfdcb9 to db57e46 Compare June 6, 2024 22:52
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.

None yet

0 participants