Skip to content
This repository has been archived by the owner on Jul 21, 2023. It is now read-only.

fix(deps): update angular monorepo #8

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 6, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular/animations 11.0.2 -> 11.2.14 age adoption passing confidence
@angular/common 11.0.2 -> 11.2.14 age adoption passing confidence
@angular/compiler 11.0.2 -> 11.2.14 age adoption passing confidence
@angular/compiler-cli (source) 11.0.2 -> 11.2.14 age adoption passing confidence
@angular/core 11.0.2 -> 11.2.14 age adoption passing confidence
@angular/forms 11.0.2 -> 11.2.14 age adoption passing confidence
@angular/platform-browser 11.0.2 -> 11.2.14 age adoption passing confidence
@angular/platform-browser-dynamic 11.0.2 -> 11.2.14 age adoption passing confidence
@angular/router (source) 11.0.2 -> 11.2.14 age adoption passing confidence
zone.js (changelog) 0.10.3 -> 0.13.1 age adoption passing confidence

Release Notes

angular/angular (@​angular/animations)

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

v11.2.12

Compare Source

v11.2.11

Compare Source

v11.2.10

Compare Source

v11.2.9

Compare Source

v11.2.8

Compare Source

v11.2.7

Compare Source

v11.2.6

Compare Source

v11.2.5

Compare Source

v11.2.4

Compare Source

v11.2.3

Compare Source

v11.2.2

Compare Source

v11.2.1

Compare Source

v11.2.0

Compare Source

v11.1.2

Compare Source

v11.1.1

Compare Source

v11.1.0

Compare Source

v11.0.9

Compare Source

v11.0.8

Compare Source

v11.0.7

Compare Source

v11.0.6

Compare Source

v11.0.5

Compare Source

v11.0.4

Compare Source

v11.0.3

Compare Source

angular/angular (zone.js)

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
Features

0.10.3 (2020-02-27)

Bug Fixes
Features
Performance Improvements

0.10.2 (2019-08-13)

Features

0.10.1 (2019-08-02)

Bug Fixes
  • zone.js: don't rely on global node typings outside of node/ directory (#​31783) (5c9a896)
  • zone.js: should expose some other internal intefaces (#​31866) (f5c605b)

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 from d54059a to ea5105a Compare January 10, 2021 04:00
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from ea5105a to b47aca2 Compare January 23, 2021 09:48
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 2 times, most recently from 7bd48ad to 151d689 Compare February 6, 2021 11:57
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 151d689 to 3d84c40 Compare February 11, 2021 07:20
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 3d84c40 to 2d044e0 Compare April 26, 2021 15:41
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 2 times, most recently from 59d3848 to cf24a4d Compare May 15, 2021 20:32
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from cf24a4d to 8813083 Compare March 7, 2022 11:37
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 8813083 to 04e07ad Compare June 18, 2022 21:01
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 04e07ad to c8bca32 Compare September 25, 2022 22:29
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from c8bca32 to 0e33f37 Compare November 20, 2022 17:55
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 0e33f37 to 49e9c13 Compare March 17, 2023 01:58
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 49e9c13 to a69a296 Compare June 12, 2023 17:15
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants