version-upper

Bump version strings in your repo


Keywords
ci, continuous-delivery, continuous-deployment, continuous-integration, pypi, pypi-package, python, python-click, python36, python37, python38, release-automation, release-management, releases, semantic-versioning, version-manager, versioning, versions
License
MIT
Install
pip install version-upper==0.0.4

Documentation

version-upper

tests Coverage Status

Primarily a reaction to bumpversion not supporting git hashes -- issue

Demo

Overview

Usage: version-upper [OPTIONS] COMMAND [ARGS]...

  A tool to update version strings in files using semantic versioning and
  commit hashes.

  Examples:

  # bump commit hash version
  version-upper bump commit_hash

  # bump patch version
  version-upper bump patch

  # bump patch version as release candidate
  version-upper bump patch --release-candidate

  # bump minor version
  version-upper bump minor

  # bump major version
  version-upper bump major

  The config file adheres to the Config Pydantic schema, and is named
  version-upper.json by default.

  Here is a sample config:
  {
      "current_version": "0.0.0",
      "current_semantic_version": "0.0.0",
      "files": []
  }

Options:
  --config TEXT  [default: version-upper.json]
  --help         Show this message and exit.

Commands:
  bump                      Bumps version strings, updates config.
  config-schema             Prints the config schema in JSON
  current-semantic-version  Prints the current semantic version
  current-version           Prints the current version
  release                   Removes rc from the version strings
  sample-config             Prints a sample config

Configuration

Create a file called version-upper.json (can be overridden using --config) like below:

{
  "current_version": "0.0.0",
  "current_semantic_version": "0.0.0",
  "files": ["main.py", "app/version.json"]
}

Be sure to add files to "files" otherwise nothing will be updated :)