-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
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
Need a --force option #131
Comments
The error message is in fact correct: bumpversion requires you to specify a [part], even when it's not needed. See #22. So this would be more correct
To me it feels weird to use a version number that your own regex is disallowing, but let's see if other people find this useful. |
Agreed, it should have been "cryptic at first", edited now.
How would that be "more correct" ?
Why wouldn't it be possible to use bumpversion as a smart "search&replace" |
The command is "more correct" in the sense that bumpversion expects a If you supply |
OK, thanks for the answer, that makes some sense now. |
Thanks for bumpversion, usually works great.
Trying to create a beta version for hamster.
Cryptic error message at first, but
from #45, it is because the
beta
is not handled by my regexps,so
--new-version
role is only to bypass the automatic increment stuff.A
--force
option would be useful here, to release right now,and think later about a regexp fix,
or just leave it at that, as releasing a beta version is exceptional for hamster.
[Edit] Summary of the request:
When
--new-version
is used, the new version should be exactly the one provided.No smart heuristics (they break too often).
An error when the new version is not compatible with the regex would be fine.
But then a
--force
option would allow to bypass this check and proceed.The text was updated successfully, but these errors were encountered: