Bump org.mariadb.jdbc:mariadb-java-client from 3.5.2 to 3.5.3

[dependabot]

Bumps org.mariadb.jdbc:mariadb-java-client from 3.5.2 to 3.5.3.

Release notes

Sourced from org.mariadb.jdbc:mariadb-java-client's releases.

MariaDB Connector/Java 3.5.3

3.5.3 (Feb 2025)

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

Changelog

Sourced from org.mariadb.jdbc:mariadb-java-client's changelog.

3.5.3 (Mar 2025)

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

Commits

• 1622933 [misc] set 3.5.3 version
• b0c299e Merge branch 'develop'
• bd1d18f [misc] zero config not permitting non plugins without hash
• ac2555b Merge branch 'develop'
• 22f8126 [misc] test improvement
• cb03a35 [misc] correcting test for MySQL user length limitation
• 031de36 [CONJ-1235] enable redirection option by default only when SSL is enabled
• 5352d6b [CONJ-1226] Dates containing zero day or month results into DateTimeException
• 2d48120 [CONJ-1243] CallableStatement.getParameterMetadata for Boolean return wrong v...
• 606fe0d [misc] code style correction
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit ed86a9a.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17 Windows

📦 extensions/hibernate-orm/deployment

✖ io.quarkus.hibernate.orm.applicationfieldaccess.PublicFieldAccessInheritanceTest.testFieldAccess - History

• Expecting actual not to be null - java.lang.AssertionError

java.lang.AssertionError: 

Expecting actual not to be null
	at io.quarkus.hibernate.orm.applicationfieldaccess.PublicFieldAccessInheritanceTest$FieldAccessEnhancedDelegate$1.assertValue(PublicFieldAccessInheritanceTest.java:141)
	at io.quarkus.hibernate.orm.applicationfieldaccess.PublicFieldAccessInheritanceTest.doTestFieldAccess(PublicFieldAccessInheritanceTest.java:100)
	at io.quarkus.hibernate.orm.applicationfieldaccess.PublicFieldAccessInheritanceTest.testFieldAccess(PublicFieldAccessInheritanceTest.java:61)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at io.quarkus.test.QuarkusUnitTest.runExtensionMethod(QuarkusUnitTest.java:521)

[geoand]

Adding the 3.20 backport label as per #48000 (comment).

Also cc @rsvoboda

[mabartos]

Adding the 3.20 backport label as per #48000 (comment).

@geoand It seems it was not backported to 3.20.x -> Not part of Quarkus 3.20.2

[geoand]

@jmartisk @gsmet ^

[gsmet]

Yeah, so from what I can see from the history of the issue, the triage/backport-3.20 was not added, until I did it today. Thus why it wasn't backported.

We will backport it in the next round. In the meantime, I think it's safe to upgrade locally.

[geoand]

Ah damn... That's on me... I commented that I would add it and then for some reason proceeded to not do so :(. I can only guess that I got distracted by something else or I made some kind of mistake in using the GH UI.

[gsmet]

Yeah, shit happens :).

I started a thread on Zulip so that we can discuss how to improve on this. I think having a ML with LTS backport requests might help. Especially since we could also send emails about our backport schedule for a given version and make sure people are aware that it's now or it will have to wait for the next round.

[mabartos]

@geoand No worries, it can happen anytime.

@gsmet Having ML for LTS backports should mitigate these cases and at least we will have some single source of truth with clear progress/plans - will be helpful for us.

We will update the MariaDB client on our side, as after discussion with @gsmet, we should be safe to do it as it's basically a version dump without any other codebase changes.

Thanks!