problem in rollback from version 4.22 to 4.21.1

[andrebotelho-warren]

Search first

• I searched and no similar issues were found

Description

My liquibase execution pipeline was using docker image with latest tag.

Some scripts were run using Liquibase version 4.22. When I rolled back to version 4.21 I started getting some errors in the liquibase status command due to a checksum difference.

What can I do to fix this? I would like the status command to work again using version 4.21.1

Steps To Reproduce

Since version 4.22 was deleted, I don't think we were able to reproduce.

But if possible, we would have to run a liquibase updatesql with version 4.22. And then, rollback to version 4.21.1 and try to run a liquibase status

Expected/Desired Behavior

Perform a rollback from version 4.22 to 4.21.1

Liquibase Version

No response

Database Vendor & Version

No response

Liquibase Integration

No response

Liquibase Extensions

No response

OS and/or Infrastructure Type/Provider

No response

Additional Context

https://docs.liquibase.com/start/release-notes/home.html

Are you willing to submit a PR?

• I'm willing to submit a PR (Thank you!)

[tati-qalified]

Hello @andrebotelho-warren , how are you?
This is a common issue, and it is one of the reasons why version 4.22 was removed. There are two things you can try:

First:

• Run clear-checksums.
• Revert to 4.21.1
• Run changelog-sync to recalculate the v8 checksums.

This will fix the checksum issue, leaving you with the prior Liquibase version.

Second:
Try updating to version 4.23.0 instead of reverting to 4.21.1, as this last release involves many improvements. You can see the release notes here.

I'll be closing this issue, though be sure to reopen it if the problem persists.

Have a good one!

[robert-gdv]

This might be related to #5761