fix(deps): update jdbi3.version to v3.53.0 (release/4.2.x)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
org.jdbi:jdbi3-core (source)	3.49.6 → 3.53.0

---

Release Notes

jdbi/jdbi (org.jdbi:jdbi3-core)

v3.53.0

Compare Source

Fixes: Jdbi-Freemarker Security Advisory GHSA-mggx-p7jf-jgw4

The Freemarker configuration allows templates to construct arbitrary
Java types, including freemarker.template.utility.Execute.

While exploiting this requires other unsafe practices (letting a user
dictate template input), it seems prudent to disable template class resolution.

Please see GHSA-mggx-p7jf-jgw4 for more details.

Upgrade to testcontainers 2.x

While this required no code changes, the testcontainers project has
renamed a number of their jar files. Jdbi still supports
testcontainers 1.x and now also testcontainers 2.x:

If you are using testcontainers with Jdbi today and can not update to
2.x, make sure that you reference the org.testcontainers:jdbc and
org.testcontainers:junit-jupiter dependencies. Those used to be
available as transitive dependency from jdbi3-testcontainers.

If you upgrade to testcontainers 2.x, the
org.testcontainers:testcontainers-jdbc and
org.testcontainers:testcontainers-junit-jupiter dependencies must be
available.

• Update testcontainers dependency to 2.0.5 (from 1.21.4)
• Add StatementContext parameter to SqlExceptionHandler and remove return value

v3.52.1

Compare Source

• fix regression for java.time.Instant mapping from 3.52.0 (#​2955, reported by @​Eng-Fouad and @​toadzky)
• Add missing mappers for java.sql.Date and java.sql.Time
• Add support for java.time.OffsetTime
• Add support for java.time.ZoneOffset

v3.52.0

Compare Source

Changes to java.time related classes

JDBC 4.2 added full support to map java.time classes onto SQL types
in 2014. This release of Jdbi switches from mapping these objects onto
"classic" (java.sql.Date, Time, Timestamp) to using the JDBC 4.2 API
(PreparedStatement#setObject and ResultSet#getObject).

These changes should not be visible for any database, except if you
were brave enough to map types with time zones or offsets
(ZonedDateTime and OffsetDateTime) onto SQL types that have no
timezone (TIMESTAMP or DATETIME). This affects databases that do
not support the TIMESTAMP WITH TIMEZONE data type. IAW MySQL.

If you use MySQL with Jdbi and map any of these data types, you are
already losing the zone/offset information. Now you actually get an
error (which is the correct behavior of the driver!) unless you load
the new MysqlPlugin which restores the mapping.

If your application relies on legacy mappings, you can also use the
new @Legacy annotation to force the old behavior. See the
documentation at https://jdbi.org/ for details.

• Add MySQL specific module (jdbi3-mysql) and plugin (MysqlPlugin).
• Add new SqlExceptionHandler hook to handle database exceptions thrown during statement execution
• Add option to not attach sensitive binding data with OpenTelemetry (#​2941, thanks @​gmellemstrand !)
• Add configuration for Jackson serialization of types with custom polymorphic handling (#​2915)
• Update to JUnit 6.0.2
• Retire Apache Derby integration (#​2866)
• Run test suite against Spring Framework 7 (#​2919)
• Add OraclePlugin that sets untyped null argument to Types.NULL for Oracle compatibility (#​1003)
• Support INOUT parameters for stored procedure Call statements (#​1606)
• Map java.time types according to JDBC 4.2 spec (using setObject) (#​988)
• Add @Legacy annotation to restore old timestamp mapping behavior
• Make @BindMethodsList work with the String template engine (fixes #​2917, reported by @​agavrilov76, fixed by @​JScodeconcise)

v3.51.0

Compare Source

• Add new jackson3 artifact for Jackson 3 ( #​2878 )

• Support configuring log level for SqlLogger (#​2901, thanks @​phinjensen! )

• Update to SLF4J 2, to allow for configurable log levels in SqlLogger (#​2902)

• Deprecate for removal installPlugins plugin discovery. It's too easy to get yourself into trouble.

• Support TYPE_USE @Nullable annotations like JSpecify ( #​2899, thanks @​protocol7 ! )

• Allow @GetGeneratedKeys on @SqlUpdate methods to return multiple results as Lists or arrays (#​2897, original PR by @​aharin, thank you!)

v3.50.0

Compare Source

JDK Baseline Update

3.50.0 is the first release of Jdbi to require Java 17. Thank you Java 11 for your service!
We intend to do occasional bug patches for significant bugs or security issues but there
will be no further active development work.

Experimental Java Native support
3.50.0 is the first release to support using Jdbi directly in native compilation. We only
support using the Java 25+ GraalVM toolchain and fully expect that there are bugs, breakages
and things that are not working well. If you use Jdbi in a native environment and find any
problems, we would be thrilled to get bug reports!

• CI verifies Jdbi runs well in GraalVM native-image (#​2476, thanks @​Eng-Fouad !)
• 3.50.0 contains no bug fixes, user visible code or API changes compared to 3.49.6.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (3.53.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.