`part` should not be required if supplying `--new-version`

This one is pretty basic, but I must be missing something in how people are using this.

Part shouldn’t be a required field if you’re supplying --new-version. It doesn’t make any sense.

If I’m at 0.1.0, and I want to go to 0.1.1, I should be able to do: bumpversion --new-version 0.1.1. I know I can just do bumpversion minor but in this scenario the version is being driven by CI so it may not be sequential.

Anyways, seems like a bug. But this project is old enough that I probably just took some crazy pills. 😃

You be the judge!

[luckydonald]

Until that is implemented/fixed specifying any part does work. $ bump2version lolwat --new-version=0.1.1

_{^{Bonus: a nice place to hide meme eastereggs in your CI flow.}}

[ederag]

To me too (as a random user feedback; the following is only what would be natural to me), 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 (#131) would allow to bypass this check and proceed.