md5sum column being update to NULL when I try to migrate from 3.5.3 to 4.8.0 or 4.9.0

So, exactly as I wrote in the title, I am trying to update my Java application to use newer version of liquibase-core library as there are vulnerabilities found in the lower versions. However, when I do upgrade my liquibase-core library and when I start migration with Liquibase#update(Contexts contexts, LabelExpression labelExpression) method, I see column md5sum in databasechangelog table being set to NULL, instead of being recalculated to someting like 8:92a9dbde7a04a1d2ee1aec16beaf0d6b. Underlying database is postgresql. Did anyone experienced someting similar? Just to mention that I am getting no errors or exceptions, it’s just md5sum column being overridden to NULL for all 3.5.3 migrations. New migrations are getting correct md5sum value, as expected.

[nvkvc]

There is a workaround for this issue: First bump 3.5.3 version to 3.6.X version (as in this version are introduced some breaking changes reg. checksum logic) After liquibase version is bumped to 3.6.X version, check your newly updated md5sum column (it should contain values something like 8:92a9dbde7a04a1d2ee1aec16beaf0d6b, comparing to previous 7:62a9cefa5a04a1d2ee1aec16beaf0d6b). After that you can safely bump to 4.8 version

FYI @kataggart

[nvkvc]

@nvkvc do all the changesets that are now NULL on databasechangelog still exist in the changelog file? Thanks

@kataggart Yes, they do exists, changelog files are still there. The only thing I updated in changelog files is that I have added logicalFilePath attribute to keep it backward compatible. Thanks