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

chore: update angular monorepo #83

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

chore: update angular monorepo #83

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 25, 2021 •
edited
Loading

This PR contains the following updates:

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

Release Notes

angular/angular (@​angular/common)

v11.2.14

Compare Source

11.2.14 (2021-05-12)
core
Commit Description
5bb7c0e fix(core): do not retain dynamically compiled components and modules (#​42003)
40cc29a fix(core): invoke profiler around ngOnDestroy lifecycle hooks (#​41969)
platform-browser
Commit Description
f66c9ae fix(platform-browser): prevent memory leak of style nodes if shadow DOM encapsulation is used (#​42005)
Special Thanks:

Alex Rickabaugh, Andrew J Asche, Georgii Dolzhykov, Joey Perrott, JoostK, Julien Marcou, Kapunahele Wong, Pete Bacon Darwin, Richard Sithole, Teri Glover, iRealNirmal, mgechev, profanis and va-stefanek

v11.2.13

Compare Source

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

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/angular-monorepo branch 5 times, most recently from 7d9a173 to c936f73 Compare August 25, 2021 09:13
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 2 times, most recently from 9b63eba to eb90fd2 Compare September 7, 2021 08:40
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 3 times, most recently from 9758d84 to c806832 Compare March 4, 2022 03:08
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from c806832 to 0c8e710 Compare June 18, 2022 19:31
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from b7ad4f0 to 9e04b37 Compare November 20, 2022 13:31
@renovate
Copy link
Author

renovate bot commented Nov 20, 2022 •
edited
Loading

⚠ 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/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: identity@0.0.1
npm error Found: zone.js@0.14.5
npm error node_modules/zone.js
npm error   zone.js@"~0.14.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer zone.js@"^0.10.2 || ^0.11.3" from @angular/core@11.2.14
npm error node_modules/@angular/core
npm error   @angular/core@"~11.2.14" from the root project
npm error   peer @angular/core@"11.2.14" from @angular/common@11.2.14
npm error   node_modules/@angular/common
npm error     @angular/common@"~11.2.14" from the root project
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-04-30T21_52_24_251Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-30T21_52_24_251Z-debug-0.log

@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 9e04b37 to e13135d Compare March 18, 2023 16:07
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from e13135d to 3aad65d Compare June 12, 2023 20:40
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 3 times, most recently from 10ae736 to 45811a4 Compare September 18, 2023 11:02
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 45811a4 to f3e7889 Compare October 26, 2023 19:09
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from f3e7889 to 5fc66a2 Compare November 3, 2023 19:29
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 5fc66a2 to 230fecd Compare January 9, 2024 18:19
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 230fecd to 70d465e Compare February 13, 2024 22:56
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 70d465e to 9942e1f Compare April 30, 2024 21:52
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 9942e1f to 443511a Compare May 17, 2024 01:58
@renovate Renovate
Copy link
Author

renovate bot commented May 17, 2024 •
edited
Loading

⚠️ 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/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: identity@0.0.1
npm error Found: zone.js@0.15.0
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.10.2 || ^0.11.3" from @angular/core@11.2.14
npm error node_modules/@angular/core
npm error   @angular/core@"~11.2.14" from the root project
npm error   peer @angular/core@"11.2.14" from @angular/common@11.2.14
npm error   node_modules/@angular/common
npm error     @angular/common@"~11.2.14" from the root project
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-21T21_49_38_149Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-08-21T21_49_38_149Z-debug-0.log

@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 443511a to d2d9195 Compare June 7, 2024 01:28
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from d2d9195 to bf6d8b7 Compare July 17, 2024 21:46
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from bf6d8b7 to 67eeb75 Compare August 5, 2024 20:07
@renovate
chore: update angular monorepo
cf2ba80 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 67eeb75 to cf2ba80 Compare August 21, 2024 21:49
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
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants