Releasing

Prerequisites

• Make sure everything being released is on the develop branch
• Make sure you are releasing from the intended commit (currently this should be the head of the develop branch since there is only one developer)
• Make sure your package.json makes sense (fix any temporary dependencies that point to file:, etc.)
• Run npm outdated - make sure any outdated packages are meant to be outdated

Qualification

• Make sure package.json has the correct version set
• Make sure you're logged into a user that can publish to @sakuraapi (npm whoami)
• Make sure documentation is up to date for release
• Make sure Travis CI is passing on develop before publishing...

Merge to Master

Automagically

• Run m2m

Manually:

• make sure tests are passing: npm test
• make sure npx nsp check passes
• make sure npm run lint is in an acceptable state
• git checkout master
• git merge <<commit hash>> --no-ff -m "merge vX.Y.Z"
• git log --first-parent --oneline
• git tag -a vX.Y.Z <<commit hash from last command>> -m “vX.Y.Z”
• Push with tags to origin

Publish NPM package

• update release notes on github
• npm publish
• close milestone