Bump your software version simply

The Justbump tool analyzes the semantic commit messages you push, creating an automatic version number. It commits the version information it creates to the TAG in the repository.

Usage

To use Justbump, you just need to act under certain rules called Semantic Commit or Conventional Commits.

Examples

feat: new big feature
^--^  ^------------^
|     |
|     +-> summary of message
|
+-------> Type: chore, docs, feat, fix, refactor, style, test, ci, build

• fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in semantic versioning).
• feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in semantic versioning).
• BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in semantic versioning). A BREAKING CHANGE can be part of commits of any type.

Examples:

Breaking change;

feat: allow provided config object to extend other configs

BREAKING CHANGE: `extends` key in config file is now used for extending other config files

Feature with scope;

feat(lang): add polish language

References:

• https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716
• https://www.conventionalcommits.org/
• https://seesparkbox.com/foundry/semantic_commit_messages
• http://karma-runner.github.io/1.0/dev/git-commit-msg.html

Docs

• https://github.com/c1982/justbump-doc/wiki/Justbump-v1.0.0

Support

• https://github.com/c1982/justbump-doc/issues