Auto publish to npm

[aenario]

It would be cool to do a npm publish at the same time we do a npm run deploy in travis.

This implies putting our secure NPM token on travis

[kosssi]

I can help for do that.

[m4dz]

Just a reminder of the actual worflow:

1. every time we push (merge included) to master or development branch, it runs a deploy to the build branch when the build/tests are ok
2. each time we want to release, I merge development into master, and update the version in the package.json file, then push it to origin/master
3. I wait for the build, then create a signed tag (is this too much?) on the build branch for this new version
4. I create a release in the GitHub interface using this tag

If this can partially or totally be automated, let's go! (or if you find a way to simplify, your suggestions are welcome :)).

Thanks guys!

[aenario]

Ok, first of all, let's document the actual worflow in this repository !
📝 publishing.md ?

It was confusing as in other apps, master is supposed to be equivalent to what's npm published. So any tag to master SHOULD trigger a NPM publish.

I'd offer to use another branch development-built, but it gets complicated fast....

[m4dz]

Al'right! I'll document in a publishing doc the actual workflow, then we could find the right way to autopublish package.

Collateral though: does signing tag for release can be considered as a good practice or is it useless?

[jsilvestre]

Keep in mind that it's something we will want to do in other apps, so I invoke @gregorylegarec @goldoraf @CPatchane. Might be worth a 1h chat with everyone to take a decision or w/e. My 2 cents :)