Workaround:
System.setProperty("liquibase.analytics.enabled", "false");

It's generally disappointing that analytics was made opt-out by default for the OSS Liquibase community. I hope there will be reconsideration about this.

@freddiN thanks for filing this issue. It is something we will take into consideration. With the various workarounds already available it is a lower priority for us right now. To get it in faster, we would accept a PR from the larger community.

@rdhzl I wrote extensively in this PR about our reasoning and why these anonymous analytics are helpful to the project overall. We have provided many ways to opt-out, and plan to continue with the current direction.

@freddiN A flag would be really nice! But even if we open the request now it will be present only in the next springboot version, so meanwhile workarounds here are still required.

@filipelautert
I perfectly understand that. Spring Boot 3.4.0 will ship with 4.29 as mentioned here (spring-projects/spring-boot#43067), and people can always choose to not upgrade or use the env.
I still think its a good idea to have all relevant configuration at one place for Spring Boot/Liquibase users, so to me enabling them to introduce another spring.liquibase.xyz property for their users to use (even if its not now, but in the forseeable future) would be a benefit.

I still think its a good idea to have all relevant configuration at one place for Spring Boot/Liquibase users, so to me enabling them to introduce another spring.liquibase.xyz property for their users to use (even if its not now, but in the forseeable future) would be a benefit.

@freddiN sorry, I didn't mean that we should not add the flag. In fact it would be good to open the PR for springboot as soon as possible so it makes it to 3.5.0 , meanwhile we can coordinate in Liquibase side to support it in SpringLiquibase class for 4.30.x+ . But until there using the System property is the way to go and it's "documented" here ;)

I also agree with @filipelautert. Adding a reminder that analytics are also only included in 4.30.x+ and are not present in any previous versions.

Liquibase PR and next steps: #6516