refactor: Bump jasmine from 6.0.0 to 6.1.0

[mtrezza]

Closes #531

Summary by CodeRabbit

• Chores
  • Updated testing framework dependency to a newer version.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement.

[parseplatformorg]

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

Status	Scan Engine	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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b2da5af7-a009-4b0e-ba0c-1ee60be8be15

📥 Commits

Reviewing files that changed from the base of the PR and between ddeafa0 and b92dc85.

📒 Files selected for processing (2)

• package-lock.json
• package.json

👮 Files not reviewed due to content moderation or server errors (1)

• package-lock.json

---

📝 Walkthrough

Walkthrough

Updates the Jasmine testing framework from version 6.0.0 to 6.1.0 in package.json and package-lock.json, including the corresponding jasmine-core transitive dependency update from 6.0.1 to 6.1.0.

Changes

Cohort / File(s)	Summary
Jasmine Version Bump package.json	Version constraint updated: jasmine 6.0.0 → 6.1.0
Lock File Updates package-lock.json	Locked versions synchronized: jasmine 6.0.0 → 6.1.0, jasmine-core 6.0.1 → 6.1.0, with corresponding resolved URLs and integrity hashes updated

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description lacks detail and required sections from the template; it only references the closed issue without explaining approach, tasks, or changes.	Expand the description to include Approach (describing the dependency update), and indicate task completion status for documentation and testing.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the primary change: bumping jasmine from 6.0.0 to 6.1.0, which is the sole focus of the pull request.
Linked Issues check	✅ Passed	The pull request successfully addresses issue #531 by updating jasmine from 6.0.0 to 6.1.0 in both package.json and package-lock.json, meeting the stated objective.
Out of Scope Changes check	✅ Passed	All changes are scoped to the jasmine dependency bump; no extraneous modifications to other dependencies, code, or configurations are present.
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

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Checkov (3.2.510)

package.json

2026-03-30 19:03:29,134 [MainThread ] [ERROR] Template file not found: package.json
2026-03-30 19:03:29,143 [MainThread ] [ERROR] Template file not found: package.json
2026-03-30 19:03:29,142 [MainThread ] [ERROR] Template file not found: package.json
2026-03-30 19:03:29,240 [MainThread ] [ERROR] Failed to invoke function /usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner. with package.json
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/checkov/common/parallelizer/parallel_runner.py", line 88, in func_wrapper
result = original_func(item)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner.py", line 74, in
results = parallel_runner.run_function(lambda f: (f, self._parse_file(f)), files_to_load)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/ope

... [truncated 2547 characters] ...

[MainThread ] [WARNI] Secret scanning: could not process file package.json
2026-03-30 19:03:29,292 [MainThread ] [ERROR] Exception traceback:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/checkov/main.py", line 647, in run
self.scan_reports = runner_registry.run(
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/runner_registry.py", line 177, in run
for result in parallel_runner_results:
File "/usr/local/lib/python3.11/dist-packages/checkov/common/parallelizer/parallel_runner.py", line 118, in _run_function_multiprocess_fork
raise v.internal_exception.with_traceback(v.internal_exception.traceback)
FileNotFoundError: [Errno 2] No such file or directory: 'package.json'

---

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 100.00%. Comparing base (ddeafa0) to head (b92dc85).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #536   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines         1172      1172           
=========================================
  Hits          1172      1172           

☔ 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 8.4.0