Authors CurseForge

Hey guys and girls,

I'm trying to push a new version of my addon to CurseForge. I used my regular workflow: change code, update version number in TOC, commit, push, create tag and push that tag. 

I expected a new version of the addon to be created now, but that didn't happen. Can someone please tell me which step I missed? I don't update this addon a lot so it's very likely that there is an additional step that I forgot...

Thanks!

In reply to olafskiii:

It's not just you, I'm having the same issue with the addon I've been maintaining.  I use the same svn process and it just acts as if I've done nothing.  I have updated branches and verified the tag pushed properly.  My guess is that there's something still off in relation to the subversion deploy process.

Thanks for the confirmation earl_parvisjam. I use Git, but I guess we can surmise that the problem is not related to the version control system we use then ;) 

Hope someone can give a solution for this because I want to put out a new version...

Mine finally updated. I think this might be a case of things just taking reeeeeealy long to process, or it getting hung up sometimes.

How long did that take? Mine still hasn't updated :(

there was a blog (i think) page about "manual" updates not being processed while the overwolf transfer was in progress but i think they may have not realised that even though we use SVN and everything on our side is automatic someone on their end needs to manually approve every package job (god that must be a painful and boring job)

either that or the packager is utterly borked (i doubt it as it been several weeks now so youd expect someone to have noticed)

I found some of my SVN revisions were gone after the transition!

And for now I can't commit codes to wowace...

My update took a little more than a day to show up.  I haven't touched it since, though I've been trying to figure out a clean way to be able to resize text from a customizable setting.  Probably won't get updated again any time soon...

my mod (arkinventory) isnt updating any more.  i can see the svn updates are getting through, but the packager just isnt doing its thing

i know curse was locked as read only for a while but thats supposed to have been ended by now

is there a better place to report packager issues?

Quote from Arkayenro >>

my mod (arkinventory) isnt updating any more.  i can see the svn updates are getting through, but the packager just isnt doing its thing

 

 

 Seeing the same here for my addon (loggerhead) also using curse svn.  I made a commit last night still has not packaged up over 12 hours later.

Mine still hasn't updated, so that's over a month now... :s

thought id look around for an overwolf place to lodge an issue for the packager but it seems like its a known issue already (not sure how long theyve known about it)

https://support.overwolf.com/en/support/solutions/articles/9000196615-curseforge-known-issues

under the wow section

i really wish theyd use email to notify authors about this stuff - you can tell whos making svn/git commits so its not super hard to work out who youd have to tell about it.

or use a site banner on the project pages

or sticky something in here

or point us to new forums if these arent going to be utilised

so many options.  i just want to be kept informed

Thanks for that info Arkayenro, that at least tells us they know about it. Hope it gets resolved soon. And then they'll have a long list of mods to package to catch up...

Quote from Burstroc >>

On Windows one of the following should force packaging on all tags/commits that haven't already packaged yet:

 

CurseForge:

curl "https://www.curseforge.com/api/projects/{projectID}/package?token={token}" -X POST -d ""

 

WowAce:

curl "https://www.wowace.com/api/projects/{projectID}/package?token={token}" -X POST -d ""

 

Replace {projectID} with your project's ID # listed in the "About" box at the top right of your project's page. Replace {token} with your api token found either here or here.

 Thanks a lot, this worked! I did change mine for PowerShell though, since I don't have curl:

Invoke-WebRequest "https://www.curseforge.com/api/projects/{projectID}/package?token={token}" -Method POST -Body ""

I am having the same problem and tried the PowerShell command:

Invoke-WebRequest "https://www.curseforge.com/api/projects/{projectID}/package?token={token}" -Method POST -Body ""

and indeed it worked :-)

I just hope I don't have to do this for every future build...