I will see if I can maneuver the packager to get to the latest tag before trying other options.
I'm dissatisfied though because there is nothing wrong with the project's Git repository -- it is properly tagged and branched and has all of the project history. The problem is the packager, but the workaround that you're suggesting is to remove history from the repository or to blow it away and recreate the repository with no tags. That seems wrong to me as a developer and I believe this is a valid complaint.
I notice that on Curse.com that each time I force a new tagged release of Ovale, that its idea of what is the latest release keeps incrementing to the next tag newer than the previous one. So, when I accidentally pushed the old tags, it thought 3.0.0 was the latest. When I pushed 5.4.25, it thought 3.0.1 was the latest, and now that I've pushed 5.4.26 it now thinks 3.0.2 is the latest.
Is there somewhere in the packager that caches what's considered the "latest" tag that can just be changed to point to 5.4.26?
I accidentally pushed all of my old tags to the CurseForge Git repository for Ovale and now the packager and Curse.com list the 3.0.1 tag as the latest release and not the actual 5.4.25 tag. How can this be fixed?