The release/publishing process is as follows:
-
Checkout
master
, rebase, and make sure it's in a clean state with no pending commits not yet pushed to origin. -
Move all entries under the UNRELEASED section in the
/CHANGELOG.md
into a new version section matching the version number that will be released.- Include the release date in the new section.
- Remove the UNRELEASED section.
-
Commit changes to
/CHANGELOG.md
using a commit message like"Changes for version x.y.z"
. -
Run
npm run release:<major|minor|patch>
. This script will first version/package.json
and the repo, and will then publish the new release to npm (as long as tests, the build, and docs succeed). It will also push the CHANGELOG commit, along with thepackage.json
version update and release tag, up toorigin
.For example, to release a new minor version, run
$ npm run release:minor
-
Update the documentation site: Happens automatically on merge to
master
branch.