Upgrade to MySQL 8.0.23

[snicoll]

No description provided.

[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

[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.

[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, liquibase/liquibase#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?

[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.

[martinvisser]

Will this be backported to 2.4.x as well?

[snicoll]

Sorry but we won't backport support of a major new release of a third party in a maintenance release.

[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 🤞