Vault 3.5.0

[vsevel]

https://github.com/quarkiverse/quarkus-vault/releases/tag/3.5.0 - Quarkus 3.8, JDK 17 + bug fix
note that the synch operation modified also assertj version to 3.25.3 (like in vault), which I did not include in this PR

[vsevel]

this build failed complaining about the synch.
should I run again, and include the assertj version change?

[vsevel]

if I ru the sync, it adds:

     <dependency>
       <groupId>org.assertj</groupId>
       <artifactId>assertj-core</artifactId>
-      <version>3.24.2</version>
+      <version>3.25.3</version>
       <scope>test</scope>
     </dependency>

what should I do @gsmet ?

[aloubyansky]

@vsevel all the changes are supposed to be added to the commit, otherwise it will fail the check. Then it'll be up to us to review the changes before merging.
If you have concerns about some of them, please add them all and add your comments for us to review. Thanks.

[aloubyansky]

It looks like that version bump in the test module comes from quarkus-vault project itself. So far looks good to me.

[vsevel]

It seemed strange to me that a bump in a test module of an ext would lead to a version change in the plateform ...

[quarkus-bot]

Status for workflow CI Build

This is the status report for running CI Build on commit 33207b7.

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

[aloubyansky]

It's a bump in the corresponding test module in the platform though. So it is consistent with the original test dependencies.

[gsmet]

Thanks!