build: update dependency jasmine-core to v6

[angular-robot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jasmine-core (source)	~5.12.0 → ~6.0.0

---

Release Notes

jasmine/jasmine (jasmine-core)

v6.0.0

Compare Source

Please see the release notes.

v5.13.0

Compare Source

Please see the release notes.

v5.12.1

Compare Source

Please see the release notes.

---

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

[angular-robot]

⚠️ Artifact update problem

Renovate failed to update artifacts 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: examples/environments/angular/project/package-lock.json

npm warn Unknown env config "verify-deps-before-run". This will stop working in the next major version of npm.
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/jasmine-core
npm error   dev jasmine-core@"~6.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jasmine-core@"^4.0.0 || ^5.0.0" from [email protected]
npm error node_modules/karma-jasmine-html-reporter
npm error   dev karma-jasmine-html-reporter@"~2.1.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/jasmine-core
npm error   peer jasmine-core@"^4.0.0 || ^5.0.0" from [email protected]
npm error   node_modules/karma-jasmine-html-reporter
npm error     dev karma-jasmine-html-reporter@"~2.1.0" 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/2026-01-19T06_12_22_591Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-01-19T06_12_22_591Z-debug-0.log

File name: report-app/package.json

Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
2026/01/19 06:12:37 Downloading https://releases.bazel.build/8.5.1/release/bazel-8.5.1-linux-x86_64...
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
Extracting Bazel installation...
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace

File name: examples/environments/angular/project/package.json

Command failed: /bin/sh -c bazel mod deps --lockfile_mode=update
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
ERROR: The 'mod' command is only supported from within a workspace (below a directory having a MODULE.bazel file).
See documentation at https://bazel.build/concepts/build-ref#workspace