Liquibase bug in LTS 3.27

[tobsebwal]

Hi everyone,
We are using the LTS versions of Quarkus and since 3.27 was released recently we have upgraded our development environments.
After upgrading from the previous LTS version to the new 3.27 version we found that liquibase complains about wrong checksums in our changesets. After some digging it is clear that this is a problem in liquibase 4.33 specifically (see also here and here).
My question is fist if this is already known and second, if there are plans to upgrade to liquibase 5.0.1 (where the bug is fixed) for Quarkus LTS 3.27?
We am aware that LTS 3.20 is still good for some time but these things can take time.

Many thanks in advance,
Tobi

[quarkus-bot[bot]]

/cc @andrejpetras (liquibase), @geoand (liquibase), @gsmet (liquibase)

[geoand]

if there are plans to upgrade to liquibase 5.0.1

We’re not upgrading to Liquibase 5 at this time due to the upstream license change to the Functional
Source License (FSL), which is source‑available and not acceptable for Quarkus (#50356 is where this was originally discussed, AFAIR).
If anything changes upstream regarding licensing, we’ll revisit and communicate the path forward.

[tobsebwal]

Thank you for the quick response! Then we will handle this on our side and hope for a backport of the fix in liquibase.

[gsmet]

This one is really problematic and the fact that they only fixed it in the relicensed version is really meh :/.

I'm more and more thinking that we should drop Liquibase from the Core, move it to the Quarkiverse and let it live its life outside of the Core with external contributors.