I used loadUpdateData with runOnChange=“true” to load static data tables. These rows are considered part of the app config and they do not change at runtime, so loadUpdateData seems like a natural choice. Previously, the checksumming would prevent these changes from re-running unless the underlying data changed or the changeSet definition changed.
Recently, without changing Liquibase versions, every one of my loadUpdateData changes marked runOnChange=“true” began re-running every time, without any changes. It isn’t harming anything in my dev environment, and I think it would be a non-issue in prod, but the unexpected behavior scares me. Has anyone else seen this?