Edit: By the way, it was a clean, straightforward commit/push in the repo. Neither update had anything weird going on. The only thing that could be related is that they were updated fairly close together (~5 minutes apart), but that's very often the case with these sort of things (when a primary consumer of the library is the same author who created it).
Your archived file seems to be only available to you, at least I can download it.
I think I have encounter similar issue like you but probably with different causes.
For me, I use SVN mostly, and for libraries, I usually set external links which link to corresponding source URL of those lib. But I also use .pkgmeta and set externals there. I know this looks to be redundant, but anyway, that works fine in the past.
Recently (actually for a few months), some of the libs will get conflict files in the auto-packaged zip. For example, the files would be something like below:
So then I disable the external settings in .pkgmeta and only use the SVN's external links, though problem seems to be the same.
My guess is that during the packaging, curseforge also check-out the codes of the project, so when I use SVN externals, it will reflect to the one curseforge checked-out.
But then the problem could be, somehow curseforge will modify the files, line-breaking style, BOM, or something else, that made the files in modified stage. And then when the libraries have updates, conflicts will happen....
I was definitely wrong with my guess to the cause of this bug in the original post; it has nothing to do with time between commits as far as I can tell. I literally cannot get this project to build correctly now regardless of timing - all new Alpha, Beta, and Release versions display this bug, which obviously makes the files unreadable by Wow.exe.
This is also affecting Rarity. I can't get the add-on to build properly as a result of this issue. Can we get an update from anyone? It's not specific to Mercurial, as it happens to only SVN repos in my example.