We have removed the 4.22.0 release of Liquibase. This version contains an updated algorithm for determining which changes Liquibase needs to deploy to a database. In some situations, the conversion to this new algorithm could result in eligible changes not being deployed to a target database.
Specifically, currently undeployed changesets with the runOnChange=true attribute may not be deployed if they were present in the first execution of Liquibase 4.22.0 against a given target database. If you have not upgraded to Liquibase 4.22.0, you are not impacted by this issue, or if you do not rely on runOnChange changesets which have changed before your upgrade.
We will soon provide more guidance on how to assess and remedy any potential impact for users who have already upgraded to Liquibase 4.22.0. If you are a Liquibase customer and believe you may be impacted by this issue, please open a ticket in our support portal at https://support.liquibase.com/