Automated semantic version releases powered by Github Issues.
$ npm install --save-dev github-semantic-version
NPM_TOKEN to CI
For example, in Travis CI's "Settings" tab for your project, you'll see:
GH_TOKEN create one in Github
You can find
NPM_TOKEN in your
3. Create labels
$ npm install --save-dev git-labelmaker
$ git-labelmaker? What is your GitHub Access Token? <paste token here>? What is your master password, to keep your access token secure? ************? Welcome to git-labelmaker!What would you like to do?> Add Labels From Package? What is the path & name of the package you want to use? ./node_modules/github-semantic-version/labels.jsonSuccessfully created 3 labels
4. Add labels to issues
Add one of the following labels to your open PRs:
As these get merged,
github-semantic-version will use this to determine
how to bump the current version.
If any un-tagged commits are pushed to
master outside of a PR, they're
automatically treated as
Once these are in place, your new versions can be pushed back to Github & NPM without permissions & security issues.
deploy:provider: scriptscript: npm run deployskip_cleanup: trueon:branch: master
If you're working on an private project, you can leave out
npm publish, which
means you have no need for your
MIT License 2016 © Eric Clemmons