Not exactly a packager problem, but I have an uploaded ZIP file on CurseForge for Ovale that was approved four hours ago, but the new release information has not propagated to Curse.com yet. Is there something else I need to do to get that working again?
I did exactly this. The packager now incrementally thinks the latest release is 3.1.16, 3.1.17, 3.1.18, etc., every time I make and push a new tag. I don't really see how this has anything to do with Git, but I guess that's just me.
No, I'm aware of how to push tags from my local repository to the Git repository on CurseForge. The problem is that when I push my tag, nothing happens. My project is in some state of limbo where it won't package because it's not approved, but it's not approved because I have no packaged files. I don't know how to resolve it.
Please kick the packager thread to create a new beta release for Ovale, which was recently tagged for "5.4.9alpha2". It didn't seem to get picked up like it normally does after getting tagged in the SVN repository.