Papertrail is not a requirement, and the version I've added as an option is free anyways.

Even if I removed it as an option, Heroku still requires any user to register a credit card.

"Credit card information is not required for free apps without add-ons. It becomes a requirement once you wish to own more than 5 apps at a time, or to use add-ons other than postgresql:dev or pgbackups:plus –– even if the add-ons are free."

It doesn't matter that Papertrail is free; its mere presence triggers the verification requirement. It didn't appear to be optional, or removable, on the deployment screen, which is where I stopped since I'm not interested in giving an entity that claims it won't charge me any money information that has no purpose other than charging me money.

They must have changed their policy, when I was developing this they required a credit card just to make an app, no matter if it was free or not.

Considering that, I'm gonna remove Papertrail from the package. It's still nice to have for debugging, although Heroku's CLI can be used just as well:

0.5.3 is out, changes:

• Removed the Papertrail addon bundle
  • This allows the app to be installed without requiring a credit card

Last night I deployed, followed the setup instructions, added the webhooks, made a tag... and of course the CurseForge packager was AFK, so I wasn't able to see if it worked. Today there's finally a package on CurseForge, so I attempted to force an update, and got this error message:
Repository "BetterBattlePetTooltip" is not tracked.

...so something isn't set up correctly. Here's my addons.json gist:
https://gist.github.com/Phanx/ce8f911fc73b67363270

The GitHub repo for the addon in question is here:
https://github.com/Phanx/BetterBattlePetTooltip

The webhook is set to "create and push", and I've triple-checked that the Curse project name and WoWI ID are correct in the gist. Where did I screw up?

You can force-update the list, it usually fixes those issues.
https://secret-journey-8122.herokuapp.com/updatelist

You also have some errors in your list:
https://gist.github.com/Phanx/ce8f91...json-L187-L215

Thanks, seems to be working now. The "updatelist" link gave this error:
...but the forced-update URL for the addon correctly uploaded to WoWI.

Fixed: https://github.com/p3lim/addon-packa...84618b35472a47

New version out for that; 0.5.4

.pkgmeta
 

Atm my addon is hosted on Curseforge using their packager. I would prefer to use this method to host on github and release on both wowi and curse at the same time.
But I wonder how I replicate the functionality of the .pkgmeta?
My current pkgmeta looks like this.

For this tool to work (in it's current implementation) you need to use the repository on both GitHub and CurseForge.

Well that is fine. but how do I do with my externals? Should I change them from externals and just embed them manually or how should I go about it?

The CurseForge packager can't deal with submodules/externals, you would still need that metadata file.

HTTP is (apparently) no longer supported on Curse; I've submitted a pull request on GitHub switching the Curse URLs over to HTTPS.

0.6.0 is out, changes:

• Now using API tokens for WoWInterface authentication, generate one here.
• CurseForge is now only accepting HTTPS connections (thanks Phanx)

Big thanks to dolby for making this happen!

0.6.1 is out, changes:

• Now using HTTPS to communicate with WoWInterface too.

CurseForge has been redesigned, I can not guarantee this project will work until I've had a look at it.

0.7.0 is out, changes:

• Fixed warnings being thrown for positive responses from WoWInterface API
• Use the new compatibility API from WoWInterface (thanks to dolby!)
• Updated parsing of CurseForge and their website updates

APP will now flag the correct compatible game versions, first by checking the interface version in the toc file, with a fallback to the default (latest) game version.

Forgot to update here for the last few versions, but here are the changes:

0.7.1 is out, changes:

• Fixed changelog not being pushed correctly.

0.7.2 is out, changes:

• Fixed interface version detection

0.7.3 is out, changes:

• Fixed force updating
• Fixed CurseForge parsing
• Added support for WowAce as a fallback when project was not found on CurseForge
• Updated entire stack to latest versions

Awesome tool, really.
I was wondering if would be possibile to polish a bit the answers for updatelist and force.

• updatelist:

  I noted that if the gist contain a broken json, no warning is given.
  Maybe an answer with
  status: (success:failure)
  data: addons.json content
  would be nice

  force:

  status: (success/failure) message: descriptive result (could be updated to version x.x.x)

Good suggestions, however I've personally switched to a different system, so this project likely won't see any updates from me in a while, aside from things like bugfixes and PRs.

The system I'm using has a detailed guide (written by me) here:
http://www.wowinterface.com/forums/s...ad.php?t=55801

Advantages are:

• No need to set up a server (Heroku) and keep it up-to-date
• Settings are stored per-project (alike the .pkgmeta), not hidden in settings/gists
• No need to poll CurseForge for updates, which can't be guaranteed
• More widely adopted by larger projects (BigWigs in particular), so it should be considered more stable/long-term available

My guide has a hard dependancy on Git, but the script can just as well be run locally (which is way harder with this proxy project)