Before the first time you release, you need to login to NPM with:
npm login
Then, every new release can be done automatically with the release script, e.g. to release a version 0.7.2:
or to just increment the minor version, e.g. from the current
That script does the following actions, aborting immediately if any of them fails:
./release 0.7.2
0.7.1
to 0.7.2
you could can omit the version argument:
./release
- runs the tests
- publishes this documentation
- updates
version
inpackage.json
- creates a release commit and a git tag for it
- pushes the source code
- publishes the NPM package