dependency: Update patch

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
com.github.ben-manes.caffeine:caffeine	3.2.0 -> 3.2.2
com.google.guava:guava	33.4.0-jre -> 33.4.8-jre
org.postgresql:postgresql (source)	42.7.5 -> 42.7.7
org.mariadb.jdbc:mariadb-java-client (source)	3.5.1 -> 3.5.5
com.eternalcode:multification-okaeri	1.2.1 -> 1.2.2
com.eternalcode:multification-bukkit	1.2.1 -> 1.2.2
com.gradleup.shadow:shadow-gradle-plugin	8.3.6 -> 8.3.9
eu.okaeri:okaeri-configs-serdes-commons	5.0.5 -> 5.0.13
eu.okaeri:okaeri-configs-yaml-snakeyaml	5.0.5 -> 5.0.13

---

Release Notes

ben-manes/caffeine (com.github.ben-manes.caffeine:caffeine)

v3.2.2: 3.2.2

• Fixed characteristics returned by Spliterators (#​1883)

v3.2.1: 3.2.1

• Fixed computeIfAbsent for an async cache's synchronous view to retry if incomplete
• Improved CaffeineSpec when being reflectively constructed (#​1839)
• Improved the handling of negative durations with variable expiration
• Fixed intermittent null after replacing a weak/soft value (#​1820)

pgjdbc/pgjdbc (org.postgresql:postgresql)

v42.7.7

Security

• security: Client Allows Fallback to Insecure Authentication Despite channelBinding=require configuration.
  Fix channel binding required handling to reject non-SASL authentication
  Previously, when channel binding was set to "require", the driver would silently ignore this
  requirement for non-SASL authentication methods. This could lead to a false sense of security
  when channel binding was explicitly requested but not actually enforced. The fix ensures that when
  channel binding is set to "require", the driver will reject connections that use
  non-SASL authentication methods or when SASL authentication has not completed properly.
  See the Security Advisory for more detail. Reported by George MacKerron
  The following CVE-2025-49146 has been issued

Added

• test: Added ChannelBindingRequiredTest to verify proper behavior of channel binding settings

v42.7.6

Features

• fix: Enhanced DatabaseMetadata.getIndexInfo() method, added index comment as REMARKS property PR #​3513

Performance Improvements

• performance: Improve ResultSetMetadata.fetchFieldMetaData by using IN row values instead of UNION ALL for improved query performance (later reverted) PR #​3510
• feat:Use a single simple query for all startup parameters, so groupStartupParameters is no longer needed PR #​3613

mariadb-corporation/mariadb-connector-j (org.mariadb.jdbc:mariadb-java-client)

v3.5.5

Compare Source

Full Changelog

Issues Resolved

• CONJ-1265 - ensure rollback and release savepoint operation to be sent to server, even when there is no transaction in progress
• CONJ-1270 - forceConnectionTimeZoneToSession doesn't always set the timezone to server

v3.5.4

Compare Source

Full Changelog

Key Enhancements

• CONJ-1261 - Added caching option for loadCodecs results to improve performance

Issues Resolved

• CONJ-1234 - Fixed incorrect type definitions in DatabaseMetaData.getTypeInfo()
• CONJ-1247 - Resolved potential race condition that could cause NullPointerException
• CONJ-1250 - avoids redundant queries for CallableStatement.getParameterMetaData()
• CONJ-1251 - Fixed SSL configuration issue where zero SSL settings only functioned without explicit SSL configuration
• CONJ-1252 - Resolved GSSAPI authentication error when server exchanges begin with 0x01 byte
• CONJ-1254 - Corrected DatabaseMetadata.getTypeInfo() returning incorrect values for AUTO_INCREMENT, FIXED_PREC_SCALE, and CASE_SENSITIVE fields
• CONJ-1255 - Fixed getString method on BIT(1) fields to properly honor transformedBitIsBoolean configuration
• CONJ-1259 - Enhanced metadata compatibility with MariaDB version 12.0
• CONJ-1260 - Improved performance of DatabaseMetaData.getExportedKeys method
• CONJ-1256 - Fixed issue to ensure correct catalog name is returned

v3.5.3

Compare Source

Full Changelog

Bugs Fixed

• CONJ-1226 Fixed issue where dates containing zero day or month resulted in a DateTimeException
• CONJ-1232 Resolved timestamp string representation incompatibility between versions 2.7 and 3.x
  • see new option oldModeNoPrecisionTimestamp
• CONJ-1226 Fixed incorrect values returned by ResultSet.getColumnType() for unsigned values
• CONJ-1241 Corrected regression in 3.x affecting column metadata for unsigned types
• CONJ-1243 Fixed CallableStatement.getParameterMetadata() returning wrong java.sql.Type for boolean values
• CONJ-1236 Prevented NPE (Null Pointer Exception) after reconnection failure in high availability configurations
• CONJ-1237 Fixed issue with incorrect statements.isClosed value after closing connection
• CONJ-1239 Disabled BULK operations when no parameters are present
• CONJ-1240 Fixed connectivity issues with databases that only accept TLSv1.3
• CONJ-1235 Modified redirection option to enable by default only when SSL is enabled

v3.5.2

Compare Source

Full Changelog

Bugs Fixed

• CONJ-1216 Resolved a performance issue that occurred when batch processing on MySQL and older MariaDB (pre-10.2) servers
• CONJ-1218 Incorrect behavior where XA connections are closed when regular connections are terminated - this is against specifications
• CONJ-1217 The trustCertificateKeyStorePassword alias parameter isn’t taken into account
• CONJ-1221 DatabaseMetadata.getTypeInfo() is missing the data types UUID and VECTOR
• CONJ-1225 System throws an exception prematurely without checking all available connections
• CONJ-1228 result-set.getObject() on BLOB type returns Blob in place of byte[]
• CONJ-660 new disconnectOnExpiredPasswords connection option that controls client behavior when connecting with an expired password.
  When set to true (default), the client disconnects if it detects an expired password.
  When false, the client maintains the connection and allows setting a new password.
• CONJ-1229 Permit executeQuery commands to not return a result-set

GradleUp/shadow (com.gradleup.shadow:shadow-gradle-plugin)

v8.3.9

Compare Source

[!WARNING]
Only Gradle 9 support is being backported to this version. No additional features or crucial bug fixes will be included in the 8.x line. Please migrate to Shadow 9 as soon as possible.

Changed

• Use BufferedOutputStream when writing the Zip file to improve performance. (#​1579)

v8.3.8

Compare Source

[!WARNING]
Only Gradle 9 support is being backported to this version. No additional features or crucial bug fixes will be included in the 8.x line. Please migrate to Shadow 9 as soon as possible.

Fixed

• Fix the regression of PropertiesFileTransformer in 8.3.7. (#​1493)

Changed

• Expose Ant as compile scope. (#​1488)

v8.3.7

Compare Source

[!WARNING]
Only Gradle 9 support is being backported to this version. No additional features or crucial bug fixes will be included in the 8.x line. Please migrate to Shadow 9 as soon as possible.

Fixed

• Fix compatibility for Gradle 9.0.0 RC1. (#​1470)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

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

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.