Update dependency karma-jasmine to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
karma-jasmine	~4.0.0 -> ~5.1.0

---

Release Notes

karma-runner/karma-jasmine (karma-jasmine)

v5.1.0

Compare Source

Features

• spec-filter: allow custom specFilter (b73dbd6)

5.0.1 (2022-05-13)

Bug Fixes

• fixes matches performance issue, github#​302 (e964fa6)

v5.0.1

Compare Source

Bug Fixes

• fixes matches performance issue, github#​302 (e964fa6)

v5.0.0

Compare Source

Bug Fixes

• limit karma peer dependency to ^6.0.0 (d72c124)

Build System

• drop Node.js 10 support (ea691e8)

Features

• deps: update dependencies including jasmine-core (821f094)

BREAKING CHANGES

• The minimum required version of karma is 6.0.0.
• The minimum required version of Node is 12.0.0.
• deps: jasmine-core was updated to the 4.1.0.

Please refer to the release notes for the complete list of changes and migration instructions.

4.0.2 (2022-03-30)

Bug Fixes

• sync package-lock.json and package.json (4dacc5d)

4.0.1 (2020-08-12)

Bug Fixes

• adapter: filter functions from result.order (#​272) (28f337c)

v4.0.2

Compare Source

Bug Fixes

• sync package-lock.json and package.json (4dacc5d)

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"4.6.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=4.4.2 <4.5" from @angular/[email protected]
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   dev @angular/compiler-cli@"13.0.2" from the root project
npm ERR!   peer @angular/compiler-cli@"^13.0.0" from @angular-devkit/[email protected]
npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev @angular-devkit/build-angular@"13.0.3" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2022-11-20T15_50_55_298Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-20T15_50_55_298Z-debug-0.log