update h2

[Siedlerchr]

User description

Closes _____

Steps to test

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [.] I manually tested my changes in running JabRef (always required)
• [.] I added JUnit tests for changes (if applicable)
• [.] I added screenshots in the PR description (if change is visible to the user)
• [.] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [.] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

---

PR Type

Enhancement

---

Description

• Update H2 database dependency from 2.3.232 to 2.4.240

• Incorporates latest H2 MVStore improvements and fixes

---

File Walkthrough

	Relevant files
Dependencies	build.gradle.kts Update H2 MVStore dependency version                                          versions/build.gradle.kts Updated com.h2database:h2-mvstore dependency version from 2.3.232 to 2.4.240 Brings in latest H2 database improvements and bug fixes +1/-1

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🟡	🎫 #13109 🔴 Make `org.jabref.logic.pseudonymization.Pseudonymization` available on the CLI Implement similar CLI experience to the consistency check Follow the implementation pattern of `org.jabref.cli.CheckConsistency` class
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Add comment about database compatibility Add a warning comment about potential backward-incompatible file format changes in the H2 database update and recommend checking release notes for migration steps. versions/build.gradle.kts [79] +// Be aware: H2 database file format changes may not be backward-compatible. +// Check release notes for migration steps before further updates. api("com.h2database:h2-mvstore:2.4.240") Apply / Chat Suggestion importance[1-10]: 8 __ Why: The suggestion raises a critical and valid point about potential data format incompatibilities when upgrading the H2 database, which could lead to significant user-facing issues like data loss or inability to downgrade.	Medium
Update