I was presuming a checksum update and the first half of the UpdateSQL file lines up with updating all of the checksum entries in the changelog.. the problem is the second half of the UpdateSQL that shows actual "SQL lines to be performed" rerunning all of those changesets. That isn't good since not all update SQL was designed to be idempotent. Now if the UpdateSQL is not accurate and the actual Liquibase update won't rerun those scripts that's "fine-ish" but I still see that as a bug..
I'm curious why liquibase would switch up checksum algos? This causes lots of issues for a large organization using the tool where any given client machine may be using some ? version of the Liquibase software so person A runs an update with 3.6.X and updates all of the checksums then person B runs another changeset with 3.5.X which now doesn't like all of the updated checksums and does.. something? I'm sure there was a convincing reason to make this change but unlike previous updates to the software this effectively makes 3.5.X and 3.6.X incompatible which is frustrating at best..