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 I have a .bumpversion.cfg with [bumpversion:file:version.txt]. When I use the --serialize cli argument, it correctly writes back to the .bumpversion.cfg but version.txt is using the serialize configuration in the .bumpversion.cfg file.
After running bump2version with --serialize, we can see that version.txt is using the serialization config from the bumpversion.cfg with the value of 0.8. And we can also see that the version in .bumpversion.cfg is using the serialization from the cli with a value of 0.8.1.
The text was updated successfully, but these errors were encountered:
Description
Hi I have a .bumpversion.cfg with
[bumpversion:file:version.txt]
. When I use the--serialize
cli argument, it correctly writes back to the .bumpversion.cfg butversion.txt
is using theserialize
configuration in the .bumpversion.cfg file.How To Reproduce Example
Step 1 create .bumpversion.cfg and version.txt
.bumpversion.cfg
version.txt:
Run bump2version
Results
version.txt:
Summary
After running bump2version with
--serialize
, we can see thatversion.txt
is using the serialization config from thebumpversion.cfg
with the value of0.8
. And we can also see that the version in.bumpversion.cfg
is using the serialization from the cli with a value of0.8.1
.The text was updated successfully, but these errors were encountered: