You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 18, 2023. It is now read-only.
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.
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).
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.
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: apiman-developer-portal@3.0.0-SNAPSHOT
npm ERR! Found: zone.js@0.13.0
npm ERR! node_modules/zone.js
npm ERR! zone.js@"0.13.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.11.4" from @angular/core@13.3.12
npm ERR! node_modules/@angular/core
npm ERR! @angular/core@"13.3.12" from the root project
npm ERR! peer @angular/core@"13.3.12" from @angular/animations@13.3.12
npm ERR! node_modules/@angular/animations
npm ERR! @angular/animations@"13.3.12" 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/2023-03-18T02_11_36_826Z-debug-0.log
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
13.3.11->13.3.1213.3.11->13.3.1213.3.11->13.3.1213.3.11->13.3.1213.3.11->13.3.1213.3.11->13.3.1213.3.11->13.3.1213.3.11->13.3.1213.3.11->13.3.120.11.8->0.13.0Release Notes
angular/angular (@angular/animations)
v13.3.12Compare Source
Breaking Changes
core
core
Special Thanks
Andrew Kushnir, Andrew Scott, George Looshch, Joey Perrott and Paul Gschwendtner
angular/angular (zone.js)
v0.13.0Compare Source
v0.12.0Compare Source
Bug Fixes
0.11.8 (2022-08-08)
Features
0.11.7 (2022-07-20)
Bug Fixes
waitForAsync(4e77c7fbf38)Features
describeblock name when raising unexpected task error (de86285)0.11.6 (2022-06-02)
Bug Fixes
processis defined when patching theGlobalErrors.install(#45392) (c7bcc1b), closes #42260Symbol.speciessafely (#45369) (e2eaac3)BREAKING CHANGES
The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking. If you usedTaskTrackingZoneSpecandchecked the pending macroTasks e.g. using
(this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask'), thenits behavior slightly changed for periodic macrotasks. For example,
previously the
setIntervalmacrotask was no longer tracked after itscallback 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
done()multiple times (#45025) (d5565cc)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
Build
BREAKING CHANGES
Object.definePropertycalls.Prior to this change, ZoneJS monkey patched
Object.definePropertyand 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
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.
This PR has been generated by Mend Renovate. View repository job log here.