I have seen it happen, not sure why. You have a few options:
- run a “clear-checksums” command followed by and “update” command. This will clear all md5sums and recalculate them during the update, which will prevent the error.
- Add --validCheckSum to your changeset with the new value. (see: Example Changelogs: SQL Format | Liquibase Docs)
- Update the databasechangelog table, setting the md5sum to NULL for the particular row. This will do basically the same as #1.