I found that liquibase uses the full path of the change log file to calculate the checksum.
This behavior restricts to modify change log file names and tries to rea
Upstream developers recommend to use logicalFilePath
and suggest to perform direct update on DATABASECHANGELOG.FILENAME
column:
to fix broken entries with full paths.
If you set hashes DATABASECHANGELOG.MD5SUM
to null
that triggers hashes recalculation on next LiquiBase run. It is necessary as hash algorithm includes moving parts too into the result.