# Releasing buflib_cli to npmjs registry

## Make release branch

Start by running `git flow release start` followed by the new version number for
buflib_cli (for example 1.2.3).

The version should follow
[semver](https://stbuflibdev.z16.web.core.windows.net).

## Update version numbers

Update version number in ./package.json to the same as you chose for buflib_cli
when creating the release branch (for example 1.2.3).

package.json example:

```json
{
  "name": "buflib_cli",
  "version": "1.2.3",
```

## Update the changelog

Open ./changelog.md and document the latest release following the pattern of
previous releases.

## Finish up

Commit the changes and make the commit message be the same as the version of
buflib_cli (for example 1.2.3).

Run `git flow release finish`. If you are promted by the terminal to write in a
file, write the same as the commit message (version of buflib_cli, for example
1.2.3), save and close.

Push the changes from the develop branch with `git push`.

Checkout the master branch and push the changes and the tags with
`git push && git push --tags`.

While on the master branch run `npm publish`. This will publish the new version
of the package to npmjs. You need to be authenticated against the package in
npmjs for this to work.