refactor: Bump jasmine from 6.2.0 to 6.3.0

[mtrezza]

Closes #257

Bumps jasmine devDependency from 6.2.0 to 6.3.0.

Changes

Routine minor update of the jasmine test runner (direct devDependency). Also bumps the transitive jasmine-core from 6.2.0 to 6.3.0.

Breaking Changes

None. This is a minor release with no breaking changes affecting this project.

Code Changes Required

None. Only package.json and package-lock.json were updated; no source or spec changes were needed.

Summary by CodeRabbit

• Chores
  • Updated the Jasmine development tooling to version 6.3.0.
  • Refreshed the associated locked package versions for consistent test execution.

[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. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[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: 92450d88-5763-4bd8-9bdb-4e7deb858264

📥 Commits

Reviewing files that changed from the base of the PR and between 814a530 and 60bd7ab.

📒 Files selected for processing (2)

• package-lock.json
• package.json

---

📝 Walkthrough

Walkthrough

The development dependency jasmine is upgraded from 6.2.0 to 6.3.0, with matching jasmine-core version, resolution, integrity, and dependency constraint updates in package-lock.json.

Changes

Jasmine dependency update

Layer / File(s)	Summary
Update Jasmine versions package.json, package-lock.json	The declared jasmine development dependency and locked jasmine/jasmine-core packages are updated from 6.2.0 to 6.3.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the required prefix and clearly summarizes the jasmine version bump.
Description check	✅ Passed	It includes the issue reference, approach, breaking-change note, and scope, with only the optional task checklist omitted.
Linked Issues check	✅ Passed	The PR updates jasmine and jasmine-core from 6.2.0 to 6.3.0 as requested in #257.
Out of Scope Changes check	✅ Passed	Only dependency and lockfile version bumps are present, with no unrelated changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	PASS: GitHub Advisory Database shows 0 advisories for jasmine-core, and Jasmine 6.3.0 notes only a bug fix, with no security changes.
Engage In Review Feedback	✅ Passed	Only author/CodeRabbit interacted; the bot approved and said there were no outstanding review threads, so no feedback was ignored.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[mtrezza]

@coderabbitai approve the PR if all review feedback is addressed and there is nothing else to do.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="parse-community/parse-server-api-mail-adapter"
pr="263"

echo "== PR metadata, files, and checks =="
gh pr view "$pr" --repo "$repo" \
  --json state,isDraft,mergeable,reviewDecision,statusCheckRollup,files,reviews,comments \
  --jq '{
    state,
    isDraft,
    mergeable,
    reviewDecision,
    files: [.files[] | {path, additions, deletions}],
    reviews: [.reviews[] | {author: .author.login, state, body, submittedAt}],
    comments: [.comments[] | {author: .author.login, body, createdAt}],
    checks: [.statusCheckRollup[]? | {name, status, conclusion}]
  }'

echo
echo "== Review threads (including resolved state) =="
gh api graphql \
  -F owner="parse-community" \
  -F name="parse-server-api-mail-adapter" \
  -F number="$pr" \
  -f query='
query($owner: String!, $name: String!, $number: Int!) {
  repository(owner: $owner, name: $name) {
    pullRequest(number: $number) {
      reviewThreads(first: 100) {
        nodes {
          isResolved
          isOutdated
          path
          line
          comments(first: 20) {
            nodes {
              author { login }
              body
              createdAt
            }
          }
        }
      }
    }
  }
}' \
  --jq '.data.repository.pullRequest.reviewThreads.nodes[] |
    {
      isResolved,
      isOutdated,
      path,
      line,
      comments: [.comments.nodes[] | {author: .author.login, body, createdAt}]
    }'

echo
echo "== Dependency diff =="
gh pr diff "$pr" --repo "$repo" -- package.json package-lock.json

Length of output: 10554

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

gh api \
  "repos/parse-community/parse-server-api-mail-adapter/pulls/263/files?per_page=100" \
  --jq '.[] | {filename, status, additions, deletions, patch}'

Length of output: 2605

---

@mtrezza Approved. The dependency and lockfile updates are consistent, there are no outstanding review threads, and all CI checks have passed.

[approve]

[mtrezza]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (814a530) to head (60bd7ab).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #263   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          159       159           
=========================================
  Hits           159       159           

☔ View full report in Codecov by Harness.
📢 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.