Comment From: psytester
Are you aware of a possible problem here due to liquibase error while using MySQL connector 8.0.23?
I had this error in another context, but since sprint-boot is using liquibase and MySQL connector too, this error could apply liquibase #1647
EDIT: Added one more issue liquibase #1639
Comment From: wilkinsona
I don't think we were aware so thanks for letting us know. If a fix to Liquibase is made, we'll upgrade in due course. Equally, if a change is made in the MySQL connector we'll upgrade in due course there as well. In the meantime, I would recommend using the liquibase.version or mysql.version properties to override the dependency versions to meet your needs.
Comment From: trajano
In my case I locked the mysql.version since that's more predicable. However, I noticed we're still on 3.10.3 of liquibase, https://github.com/liquibase/liquibase/issues/1639 does not seem like they included the fix in the 3.x line, were there major incompatibilities that we have to be aware of which is why 4.x is not in the BOM?
Comment From: wilkinsona
@trajano There aren't many major incompatibilities in 4.x and for many it will be a drop-in replacement. We've upgraded to it in 2.5.
Comment From: martinvisser
Will this be backported to 2.4.x as well?
Comment From: snicoll
@martinvisser please consider searching the issue tracker before asking such a question (#25219).
Comment From: martinvisser
@snicoll I should have indeed! :) Thanks for the quick reply. But I actually ment the upgrade of liquibase to 4.x, not the mysql connector upgrade.
Comment From: snicoll
Sorry but we won't backport support of a major new release of a third party in a maintenance release.
Comment From: martinvisser
Okay, good to know. It seems there are no issues in upgrading liquibase locally, so we will just go ahead with that and will upgrade to Spring Boot 2.5 in due time.
Comment From: deleze
I have create a PR liquibase/liquibase#1720 to back port the fix on 3.10.x. I hope that the liquibase team will build a 3.10.4 🤞