Repository URLs are slug-based. The API is currently the only endpoint that I'm aware of that is ID-based. I've actually had the internal server error a couple of times, but subsequent pushes did what was expected. Not ideal, and something the devs need to work on, but not world-ending. If this isn't your experience, please report.
So I was able to push a few successful changes after the migration using hg (so I know it has worked before), but today all I'm getting are these same 500 errors. No changes to the settings on my end. :(
if it's a critical fix for your addon(s), i suggest you try to package the zip file yourself and upload that zip to curseforge... maybe that works until they fix things.
take time to verify that the zip file that ends up published is what you intend to publish though because after the migration curseforge is altering uploaded zip files before publishing them. (hopefully they will disable this new behaviour sometime soon)
I've got mercurial version 3.7.3 running. I'm trying to push 4 commits to the remote. The commit changes include adding one new sub-folder and file, renaming (moving) a few existing files, and a few edits on existing files.
This is the repo:
the specific error is
hg push --new-branch default
pushing to https://repos.curseforge.com/wow/prospect-me/
searching for changes
abort: HTTP Error 500: Internal Server Error
Completed with errors, see above