version

boltify version

Bump version of packages changed since the last release

Usage

boltify version       # select from prompt(s)

Options

• --amend
• --git-remote
• --message
• --no-commit-hooks
• --no-git-tag-version
• --no-push

--amend

boltify version --amend
# commit message is retained, and `git push` is skipped.

When run with this flag, boltify version will perform all changes on the current commit, instead of adding a new one. This is useful during Continuous integration (CI) to reduce the number of commits in the project's history.

In order to prevent unintended overwrites, this command will skip git push (i.e., it implies --no-push).

--git-remote <name>

boltify version --git-remote upstream

When run with this flag, boltify version will push the git changes to the specified remote instead of origin.

--message <msg>

This option is aliased to -m for parity with git commit.

boltify version -m "chore(release): publish %s"
# commit message = "chore(release): publish v1.0.0"

boltify version -m "chore(release): publish %v"
# commit message = "chore(release): publish 1.0.0"

# When versioning packages independently, no placeholders are replaced
boltify version -m "chore(release): publish"
# commit message = "chore(release): publish
#
# - [email protected]
# - [email protected]"

If the message contains %s, it will be replaced with the new global version version number prefixed with a "v". If the message contains %v, it will be replaced with the new global version version number without the leading "v". Note that this placeholder interpolation only applies when using the default "fixed" versioning mode, as there is no "global" version to interpolate when versioning independently.

--no-commit-hooks

By default, boltify version will allow git commit hooks to run when committing version changes. Pass --no-commit-hooks to disable this behavior.

This option is analogous to the npm version option --commit-hooks, just inverted.

--no-git-tag-version

By default, boltify version will commit changes to package.json files and tag the release. Pass --no-git-tag-version to disable the behavior.

This option is analogous to the npm version option --git-tag-version, just inverted.

--no-push

By default, boltify version will push the committed and tagged changes to the configured git remote. Pass --no-push to disable this behavior.

--sign-git-commit

This option is analogous to the npm version option of the same name.

--sign-git-tag

This option is analogous to the npm version option of the same name.