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....