-
When I run the same command using `--dry-run` it executes without the part positional argument added.
Also running with `--verbose` option it works fine.
Sample command
`bumpversion --all…
-
It's my configure following:
```
[bumpversion]
current_version = 0.1.1-dev
commit = False
tag = True
tag_name = 'v{new_version}'
message = 'Bump version: {current_version} → {new_version}'
p…
-
I get this error message, when a file is changed by the
[bumpversion:file:simlink_file]
option:
fatal: pathspec 'some/file' is beyond a symbolic link
Traceback (most recent call last):
Fi…
-
Build an analogous script to https://github.com/NorESMhub/ccs_config_noresm/blob/noresm/.github/workflows/bumpversion.yml
-
I run:
```
bumpversion --config .bumpversion.cfg --new-version 0.5.2
```
My config:
```
[bumpversion]
files = README.rst docs/Makefile docs/make.py hddm/__init__.py
commit = True
tag = True
current…
-
Pretty sure older versions showed a diff. For sure bumpversion showed a diff.
Current output:
```
> bumpversion patch --dry-run --verbose --list …
-
I want to also bump release number of spec file, but it was on separate line. e.g.
```
Version: 0.5.0
Release: 1{?%dist}
```
My `.bumpversion.cfg`
```
[bumpversion]
current_version = 0.5.0
…
vooon updated
4 years ago
-
Is there a way to prevent pre-release tags from appearing if the major verison is 0 (i.e. rapid development?). As it stands, my `.bumpversion.cfg` is
```
[bumpversion]
current_version = 0.0.0
ta…
-
This is my first time using `bumpversion` and I can't get a release_name bump to be the first value in a list. My goal is to use `bumpversion release_name` to go from d.d.d to d.d.d-foo.
Here's my …
-
Using:
- Python 3.5.4 :: Continuum Analytics, Inc.
- Successfully installed bumpversion-0.5.3
Repeat of #13, not #18, #40, etc.
```
bumpversion --help
```
```python
> bumpversion --hel…