How it works

No black magic. In semantic-release you don't have full control of project publish, semantic-release smartly analyze your commits and publish the corresponding new version.

While using kanpai (shortened to kp), you specify the version to publish instead. By running kp [patch|minor|major|x.y.z], it does following things:

• Check git status, see if you have committed the changes and if the remote history differs.
• Run tests, npm test by default.
• Update package version, CHANGELOG.md, create git tag as well.
• Push to remote git server

After that, you can publish the npm package and create GitHub Release with the kp release command. And this step can be automated via CI like GitHub Actions and CircleCI.

Install

$ npm install -g kanpai

# or use yarn
$ yarn global add kanpai

Usage

$ kp [patch|minor|major|$version|pre$type]

# custom test command, equal to npm run test:other
$ kp --test test:other

# skip test script
$ kp --skip-test

# more usages
$ kp -h

A common workflow:

# after hack something...
$ git commit -am "change the world"
$ kp

# On CI
$ kp release

Config

Some CLI flags can be configured via kanpai.json file:

{
  "test": "lint", // custom test script => npm run lint
    "commitMessage": "Release version %s"
}

Keep a CHANGELOG.md

Running kp will also generate a CHANGELOG.md file, which will include the changes since last release:

## Unreleased

No unreleased changes.

## 0.1.0

- Some commit message

As you can see this file also includes an "Unreleased" section, and upon running kp the content will be automatically replaced by the commit messages since last release, and the heading ## Unreleased will be updated to the actual version number.

You can also write the "Unreleased" section manually, the content will only be replaced by commit messages if the heading is followed by nothing or another h2 heading. In this case only the heading will be replaced.

FAQ

fatal: no upstream configured for branch 'master'

Two options:

a) git branch --set-upstream-to=origin/master master and then run git push
b) git push -u origin master

License

MIT © EGOIST

Changelog

Unreleased

No unreleased changes.

0.11.0

• Removed kp get and kp set commands, basically we removed the global config. Config can only be done via kanpai.json or the kanpai field in package.json.
• Fix: populate changelog with git commit history when there's no manually added changelog, by @LittleSound via #32

0.10.1

• Support HTTPS git URL.

0.10.0

• Move npm publish and kp gh-release to a standalone command: kp release, now running kp will only update package.json, create git tag and push to GitHub. kp release is used to actually publish on npm and create release on GitHub, this step could be automated via CI instead, env variables GITHUB_TOKEN and NPM_TOKEN are required for this to work.
• Generate default changelog from commit messages.

0.9.9

• Missing changelog body on GitHub Releases.

0.9.8

• Add kp gh-release command to publish a new release on GitHub.
• Migrate this package to esm format.

0.9.7

• Fix first release again

0.9.6

• Fix changelog heading

0.9.5

• Fix first release
• Prepend ## Unreleased to the top of the changelog

0.9.4

• Remove v prefix from default version number in CHANGELOG.md

0.9.3

• Make sure git push tags too

0.9.2

• Replace %s in commit message with actual version number.

0.9.1

• Require version to be specified to prevent accidentally running kp
• Automatically change title ## Unreleased in CHANGELOG.md to actual version ## vx.y.z when publishing