Closed juanalot closed 6 years ago
Yes, makes sense. We have the same preferences wrt/ command line utilities.
Maybe you can use the --search
and --replace
flags to tell bumpversion
to match the whole file. IIRC for parsing, bumping and serializing the defaults should match your semver use case.
Thanks for the prompt reply. Wanted to remove our custom code to replace it with a one-liner in the build, but timebox ended.
In the root of my repo I have a file named
version
. This file contains a semver string on line 1. That is all.I expected the command
bumpversion patch version
to work. I do not want to use any cfg files. I simply expect the command to read the semver string, e.g. 2.0.38 and change it to 2.0.39.Is this not the most basic use case? If the current version is already in the file why do I need to specify it? And by using something called 'bumpversion' one expects it to know how to calculate the new version. What am I missing?
Edit:
To be clear, I expected
bumpversion patch version
to do what I do in my own scripts/bump_version.py