You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, it's very likely what I'm seeing is user error, but I'm having trouble figuring out how exactly to get the result that I'm looking for. Really all I want to do is add an addition part to the end of a typical semvar versioning scheme to correlate to commit number after the last version bump. I plan to have this automatically get bumped in our repo CI. Here's what my config looks like:
What I'm seeing is that when I run bumpversion commit with this config, the current_version in my config file is updated as I expect to 1.3.8.1. But in the other configured files (setup.py and repo/version.py), the version is being changed to 1.3.8.1.0. I tried adding the parse/serialize keys to the individual file configs, but I get the same result. Any idea what is going on here?
Thank you in advance!
The text was updated successfully, but these errors were encountered:
Hi all, it's very likely what I'm seeing is user error, but I'm having trouble figuring out how exactly to get the result that I'm looking for. Really all I want to do is add an addition part to the end of a typical semvar versioning scheme to correlate to commit number after the last version bump. I plan to have this automatically get bumped in our repo CI. Here's what my config looks like:
What I'm seeing is that when I run
bumpversion commit
with this config, thecurrent_version
in my config file is updated as I expect to1.3.8.1
. But in the other configured files (setup.py
andrepo/version.py
), the version is being changed to1.3.8.1.0
. I tried adding theparse/serialize
keys to the individual file configs, but I get the same result. Any idea what is going on here?Thank you in advance!
The text was updated successfully, but these errors were encountered: