We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
You can't just run bump2version --new-version 0.1.7
bump2version --new-version 0.1.7
Reading config file setup.cfg: [bumpversion] current_version = 0.1.6 commit = True tag = True [bumpversion:file:deeppath/__init__.py] search = __version__ = "{current_version}" replace = __version__ = "{new_version}" [bdist_wheel] universal = 1 [flake8] exclude = docs [aliases] test = pytest [tool:pytest] collect_ignore = ['setup.py'] usage: bumpversion [-h] [--config-file FILE] [--verbose] [--list] [--allow-dirty] [--parse REGEX] [--serialize FORMAT] [--search SEARCH] [--replace REPLACE] [--current-version VERSION] [--no-configured-files] [--dry-run] --new-version VERSION [--commit | --no-commit] [--tag | --no-tag] [--sign-tags | --no-sign-tags] [--tag-name TAG_NAME] [--tag-message TAG_MESSAGE] [--message COMMIT_MSG] [--commit-args COMMIT_ARGS] part [file [file ...]] bumpversion: error: the following arguments are required: part
From what I can see when I use --new-version that I am giving the whole version not part of it, so why is it mandatory?
--new-version
The text was updated successfully, but these errors were encountered:
Stumbled upon this as well.
Same issue as #22
Sorry, something went wrong.
No branches or pull requests
You can't just run
bump2version --new-version 0.1.7
From what I can see when I use
--new-version
that I am giving the whole version not part of it, so why is it mandatory?The text was updated successfully, but these errors were encountered: