The problem is, the database changelog was created with a custom build which may in fact be the cause of its corruption. Testing it with an official build and saying "it doesn't work any more" may just mean "The unofficial build broke it, and it doesn't work with the official build now."
This is my point: You need to start from scratch when testing something with the official build. As you said, if you delete your changelog, the official build seems to work fine so far according to your description. Verifying that a file broken from an unofficial build doesn't work with official builds isn't verifying that the problem is present in the official build. You'd need to verify that the official build breaks the changelog itself.
It's very similar to saying "X build corrupted my MP3 file from a recording, and when I copied it over to the current build, it couldn't play the MP3 file either so it must also be a bug in the current build." It doesn't work that way, you'd need to re-produce the original conditions for creating that MP3 with the current build and see if it still comes up corrupted.