Bump apicurio-registry.version from 2.4.7.Final to 2.4.13.Final

[dependabot]

Bumps apicurio-registry.version from 2.4.7.Final to 2.4.13.Final.
Updates io.apicurio:apicurio-registry-client from 2.4.7.Final to 2.4.13.Final

Release notes

Sourced from io.apicurio:apicurio-registry-client's releases.

2.4.12.Final

No changelog for this release.

2.4.11.Final

No changelog for this release.

2.4.10.Final

No changelog for this release.

2.4.9.Final

Full Changelog: Apicurio/apicurio-registry@2.4.7.Final...2.4.9.Final

Commits

• See full diff in compare view

Updates io.apicurio:apicurio-registry-serdes-avro-serde from 2.4.7.Final to 2.4.13.Final

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)

[gsmet]

@ozangunalp this update looks OK to me, should we update? If not, let's close it to free Dependabot slots.

[ozangunalp]

@gsmet Thanks for the heads up.

I've rebased and bumped the version to 2.4.14.Final. Also, slide in another related change.

[github-actions]

🙈 The PR is closed and the preview is expired.

[ozangunalp]

@cescoffier is the mailer VT test flaky? I'll rebase this and retry the CI. it seems to fail-stop early.

[cescoffier]

Yes, that test might be flaky. We need to revisit the VT tests - we fixed some issues, but there are still a few.

[quarkus-bot]

Failing Jobs - Building 9e7b2c1

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✔️	Gradle Tests - JDK 11
✖	Gradle Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs	Build scan
✖	JVM Tests - JDK 11	Build	⚠️ Check →	Logs	Raw logs
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs	Build scan
✖	JVM Tests - JDK 21	Build	Failures	Logs	Raw logs	Build scan

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

✖ io.quarkus.gradle.devmode.BasicKotlinApplicationModuleDevModeTest.main line 19 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeClient was not fulfilled within 1 minutes  30 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

✖ io.quarkus.gradle.devmode.KotlinProjectWithCompilerArgsDevModeTest.main line 17 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeClient was not fulfilled within 2 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

---

⚙️ JVM Tests - JDK 17 #

- Failing: integration-tests/hibernate-orm-compatibility-5.6/mariadb integration-tests/hibernate-orm-compatibility-5.6/postgresql 

📦 integration-tests/hibernate-orm-compatibility-5.6/mariadb

✖ io.quarkus.it.hibernate.compatibility.CompatibilityTest.offsetTime line 122 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: 

expected: 11:58:30+01:00

📦 integration-tests/hibernate-orm-compatibility-5.6/postgresql

✖ io.quarkus.it.hibernate.compatibility.CompatibilityTest.offsetTime line 122 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: 

expected: 11:58:30+01:00

---

⚙️ JVM Tests - JDK 21 #

- Failing: integration-tests/hibernate-orm-compatibility-5.6/mariadb integration-tests/hibernate-orm-compatibility-5.6/postgresql 

📦 integration-tests/hibernate-orm-compatibility-5.6/mariadb

✖ io.quarkus.it.hibernate.compatibility.CompatibilityTest.offsetTime line 122 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: 

expected: 11:58:30+01:00

📦 integration-tests/hibernate-orm-compatibility-5.6/postgresql

✖ io.quarkus.it.hibernate.compatibility.CompatibilityTest.offsetTime line 122 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: 

expected: 11:58:30+01:00

[ozangunalp]

Failing tests aren't related, merging it