Tag releases that go to NPM

appnexus / sicksync

Don’t accept the available as the preferable. Go the extra mile with extra speed.

Apache License 2.0

68 stars 11 forks source link

Tag releases that go to NPM #5

Closed jondlm closed 9 years ago

jondlm commented 9 years ago

Each change to the version of package.json and npm publish should correspond to a pushed git tag -a v1.0.0 -m 'Releasing 1.0.0' to line things up cleanly with github.

You could also use the npm version [ major | minor | patch ] function for a shortcut. It does the package.json modification and git tagging for you in one step. You'll still have to push the tag and publish the package to npm though.

joelgriffith commented 9 years ago

That is super handy. Going to have a 1.0.1 release here soon if I can get to the bottom of the memory leak...