I tagget last release of GarrisonCommander (2.5.14)
It appears in curseforge as Type release and status new
I noticed that it's the only one in this status (the other ones are approved) and also it has no checkbox so I no clue on how I could approve it (if approving is necessary, which would be a pain, anyway, tagging should be enough.
In curse it says addon was updated but the release offered for download is still 2.15.3
Sincerely, the old packager was slow and sometimes got stuck, but at least you could have an insight on its attivity from status page.
Now we are blind.
Also removing ssh access broke eclipse egit.
Really, while I understand the need to make new interface for general sites, this one is for developer and it was really better in the old way.
Torhal: Thanks, I did but it's very minimal... just "requested, processing, processed, completed".
There is no clue at all on what went wrong.
I didnt retag the project to nhot make things worst but I just fixed a nasty bug and really would like to update the addon. Should I make a new tag? Sometimes doing this with the old packager restarted the queue and bit tags were processed