Automates NPM publication #48
Conversation
Additionally, * updates CHANGELOG for new release * fixes CHANGELOG formatting * sets new release: 0.6.1
| @@ -14,6 +14,15 @@ before_script: | |||
| script: | |||
| - gulp | |||
|
|
|||
| deploy: | |||
| provider: npm | |||
| email: "john@radify.io" | |||
There was a problem hiding this comment.
I've just set up shipping@radify.io as an email group that we can use for stuff like this, so that no one becomes a single point of failure.
There was a problem hiding this comment.
@nateabele If we use shipping@radify.io, that email will also need to have a Github account, an NPM account, and an NPM API key. Regarding, npm publish, no one person can become a single point of failure so long as multiple contributors are listed in package.json and on the npmjs.com website. Regarding automated Travis publication, my credentials could become a point of failure if I changed by NPM API key, but even that could be fixed with a simple change of the .travis.yml. Should we go ahead & switch to shipping@radify.io? Additionally, I'm looking into NPM Organizations, which seems to be a new thing:tm:, and might solve problems like this for us.
Automates NPM publication
Description
Test Script