Starting in SpringBoot 3.4.4 there is a problem when using the managed-dependencies for Liquibase and Postgresql IF the Postgresql database name is all caps (i.e. "FOOBAR").
https://github.com/liquibase/liquibase/issues/6666
This has now been resolved and tested with the following versions:
liquibase: 4.32.0 postgresql: 42.7.6
It would be great if the next spring-boot version would update to at least these versions to be able avoid having to override them in project.
Comment From: wilkinsona
We won't upgrade to a new minor version of Liquibase in a Spring Boot maintenance release. As such, we'll pick up Liquibase 4.32 (or later) in due course as part of Spring Boot 4.0.
We'll upgrade to Postgres 42.7.6 as a matter of course as part of this month's round of maintenance releases.
Comment From: marcelstoer
Things just got a bit more complicated due to https://github.com/advisories/GHSA-hq9p-pm7w-8p54.
Due to https://github.com/liquibase/liquibase/issues/6666 you must either stick to PG <=42.7.4 or bump Liquibase to >=4.32. However, due to https://github.com/advisories/GHSA-hq9p-pm7w-8p54 you'll want PG 42.7.7.
Comment From: isuftin
@marcelstoer - Can you verify 42.7.7 w/ LB 4.32.0? https://github.com/liquibase/liquibase/issues/6666#issuecomment-2970604283
Comment From: marcelstoer
@isuftin I didn't even try as we decided to not manage Liquibase ourselves → we get it through Spring Boot → we're stuck at 4.29. This also means we're stuck at PG 42.7.4 (we suppressed its vulnerability due not affected).