Update dependency jasmine-core to ~4.2.0 - autoclosed

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jasmine-core (source)	`~4.0.0` -> `~4.2.0`

Release Notes

jasmine/jasmine

### [`v4.2.0`](https://togithub.com/jasmine/jasmine/releases/tag/v4.2.0) [Compare Source](https://togithub.com/jasmine/jasmine/compare/v4.1.1...v4.2.0) Please see the [release notes](https://togithub.com/jasmine/jasmine/blob/main/release_notes/4.2.0.md). ### [`v4.1.1`](https://togithub.com/jasmine/jasmine/releases/tag/v4.1.1) [Compare Source](https://togithub.com/jasmine/jasmine/compare/v4.1.0...v4.1.1) Please see the [release notes](https://togithub.com/jasmine/jasmine/blob/main/release_notes/4.1.1.md). ### [`v4.1.0`](https://togithub.com/jasmine/jasmine/releases/tag/v4.1.0) [Compare Source](https://togithub.com/jasmine/jasmine/compare/v4.0.1...v4.1.0) Please see the [release notes](https://togithub.com/jasmine/jasmine/blob/main/release_notes/4.1.0.md). ### [`v4.0.1`](https://togithub.com/jasmine/jasmine/releases/tag/v4.0.1) [Compare Source](https://togithub.com/jasmine/jasmine/compare/v4.0.0...v4.0.1) Please see the [release notes](https://togithub.com/jasmine/jasmine/blob/main/release_notes/4.0.1.md).

Configuration

📅 Schedule: Branch creation - "after 8am and before 5pm on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled due to failing status checks.

♻ 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.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

⚠ 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 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-12T03_30_46_597Z-debug-0.log

mycomplexsoul / delta