Different issue, will be fixed shortly (super ckk is on it! ahhh)
Not to derail my own thread, but since it was mentioned, I'll add this:
I've received 9 duplicate updates just now telling me a ticket was posted to my add-on. The updates are all identical except the timestamp. They keep coming approximately every minute, I don't know how many more I'm going to get. This could get annoying fast.... heh.
I'm not sure if the packager is running slowly, incorrectly or not at all. I uploaded a revised version of my addon last night and then tagged it for release and it did not update the downloadable version via the corresponding Curse page.
I then commited another update this morning and then tagged that again for release and it then created the downloadable version for the previous night's update but so far, not for the one from this morning.
I'm not sure if I'm seeing a problem or not being patient enough. My prior experience had always been of near-instant packaging and propagation through to Curse therefore these delays and unusual behaviours have caught my attention.
As I type this update, my project page and the corresponding Curse download page show version 3.48 of my addon being the most 'up-to-date' copy however the version I uploaded this morning is 3.49 and I can confirm this by browsing the SVN tags folder manually.
Since it is now approximately five hours after the time of the upload I would guess the packager is at fault (or some component related to it) because I would assume, hopefully safely, that five hours is enough time to allow the server running the packager to do whatever else it might be doing when busy and to allow it to get around to packaging my code-releases.
So, now I wonder, if the packager (whatever it is in terms of a piece of software) can be restarted and then automatically package my latest code-release or is some more manual form of intervention required to get things back into sync for me... and if so, do I need to do anything more than the posts I have made in this thread?