Quarkus 3.8 LTS upgrade
In early July, Quarkus 3.2 will no longer recieve security updates as it will reach it's 1 year end of life. At that point, we will need to migrate to the new LTS of Quarkus 3.8. There is currently one breaking change that may impact us, though investigation will be needed to check the scope of the impact. The migration guides and one of the guides mentions that anything below the announced minimums will cause the API to fail to start (https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.5#hibernate-orm), though it is mentioned if you explicitly set the version that older versions may start though they could experience issues.
The only DB that should be on the old MariaDB version is one of our internal API DBs that isn't exposed to the public, so we might be able to branch our release and do fix backports in the short term in the worst case scenario.