Update h2 to 2.4.240

[scala-steward]

About this PR

📦 Updates com.h2database:h2 from 2.3.232 to 2.4.240

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "com.h2database", artifactId = "h2" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.h2database", artifactId = "h2" }
}]

^{labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1}

[coderabbitai]

📝 Walkthrough

Walkthrough

The H2 test dependency version in build.sbt was updated from 2.3.232 to 2.4.240. No other files or configurations were changed.

Changes

Cohort / File(s)	Summary of Changes
Build configuration build.sbt	Bumped H2 test dependency version from 2.3.232 to 2.4.240.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update h2 to 2.3.230 #349 — Also updates the H2 test dependency in build.sbt.
• Update h2 to 2.3.232 #356 — Prior H2 version bump in build.sbt; same dependency line affected.

Poem

I nudge the knob from two-three-two, to two-four-two-four, shiny new.
In test-tube lands where queries brew,
The jars line up, the builds ensue.
A hop, a bump, a version cue—
Thump-thump goes CI: all tests through! 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title concisely and accurately summarizes the main change of updating the H2 database dependency to version 2.4.240, clearly reflecting the primary intent of the pull request.
Description Check	✅ Passed	The description clearly explains that the PR updates the com.h2database:h2 test dependency to version 2.4.240, aligns with the changeset, and provides usage instructions and context relevant to the update.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 18b6b69 and eb7116a.

📒 Files selected for processing (1)

• build.sbt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Summary

🔇 Additional comments (1)

build.sbt (1)

15-15: Ensure H2 upgrade doesn’t break the cross-Scala test matrix Rerun the full test suite under each supported Scala version (2.12.20, 2.13.16, 3.3.6) to confirm nothing regressed after bumping to 2.4.240.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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