refactor: Bump jasmine from 5.13.0 to 6.0.0

[dependabot]

Bumps jasmine from 5.13.0 to 6.0.0.

Release notes

Sourced from jasmine's releases.

v6.0.0

Please see the release notes.

v6.0.0-beta.0

Please see the release notes.

v6.0.0-alpha.2

Please see the release notes.

v6.0.0-alpha.1

Please see the release notes.

v6.0.0-alpha.0

Please see the release notes.

Commits

• 834995b Bump version to 6.0.0
• 861cf8d Update copyright date
• c3fab6f Depend on @​jasminejs/reporters 1.0.0
• dd71217 Merge branch '6.0'
• 77481bc Bump version to 6.0.0-beta.0
• 49ae9a2 Merge branch 'no-console-reporter' into 6.0
• 16e6219 Depend on published reporters package
• 90e13fc Respect the NO_COLOR env var
• 6fac6ad Move ConsoleReporter to another package
• 292233b Tighten up eslint config
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

• Chores
  • Updated Jasmine testing framework to version 6.0.0 for improved development tooling.

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[mtrezza]

Review findings for jasmine 5.13.0 → 6.0.0:

Breaking changes in jasmine 6.0.0:

1. Config file loading: Only the first config file is loaded when multiple are present. This project has both jasmine.json and jasmine.js, but jasmine.js is a helper loaded via the helpers config in jasmine.json, not a standalone config file. All CI tests pass.
2. ConsoleReporter removed: Moved to @jasminejs/reporters. Not used in this project.
3. Node 18 support dropped: Tests still pass on Node 18 in CI (unofficial support continues).

All CI checks pass. This PR is good to merge.

[mtrezza]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Jasmine devDependency version updated from 5.13.0 to 6.0.0 in package.json. No runtime logic or behavioral changes introduced.

Changes

Cohort / File(s)	Summary
Dependency Update package.json	Jasmine devDependency bumped from 5.13.0 to 6.0.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and accurately describes the main change: bumping the jasmine devDependency from version 5.13.0 to 6.0.0, which is the sole modification in the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dependabot/npm_and_yarn/jasmine-6.0.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.19%. Comparing base (125b3f3) to head (a245e54).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #436   +/-   ##
=======================================
  Coverage   97.19%   97.19%           
=======================================
  Files           2        2           
  Lines         214      214           
=======================================
  Hits          208      208           
  Misses          6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[parseplatformorg]

🎉 This change has been released in version 5.0.0