Bug in v4.21+ changesets are not run because AbstractUpdateCommandStep.isUpToDateFastCheck incorrectly caches value across schemas

@jglass and @Hylke - there have been a series of updates to Liquibase recently that address checksum issues. Please try Liquibase 4.23.0 or later to see if that addresses your issue.

Note: the upcoming Liquibase 4.23.1 release (on track for a mid-August) handles a few more checksum-related edge cases if the 4.23.0 release doesn’t fully resolve the issues you’re currently experiencing.