2026.06 uses/depends on Spring Boot 4.0 which in turn include Liquibase 5.x
Due to the changed license, we can’t use Liquibase 5.x any more.
Is there a recommended approach by the A12 team on how to lock the dependency to Liquibase to 4.?
Or is this done automatically when including the A12DS module?
hi @thomas-soft-grove
From Data Services side, we already forced liquibase version down to 4.x by this:
configurations.configureEach {
// Keep Liquibase on the 4.x line from the version catalog even though the Spring Boot BOM
// manages 5.x. Spring Boot 3.x runs against either, but Data Services ships 4.x for now.
resolutionStrategy.eachDependency { details ->
if (details.requested.group == 'org.liquibase') {
details.useVersion libs.liquibaseCore.get().version
details.because 'Data Services ships Liquibase 4.x; do not follow Spring Boot BOM to 5.x'
}
}
}
Ah, great. Thanks for the quick answer!