Manually bump entire version, not just manually specify which part to increment

The docs state that the version can be manually bumped but I believe this is incorrect as there’s no other mention of this in the docs or in the CLI help beyond --increment {MAJOR,MINOR,PATCH} which is merely specifying the part to auto-increment.

Why do I want to manually specify the version to bump to? Well, I don’t but unfortunately, dev versions are not supported - but I still want to make use of commitizen’s version-updating inside of files. Otherwise, I will need to use a separate tool in conjunction, such as bumpversion.

I want to be able to do cz bump 1.0.1 for example (optional positional arg or --manual <foo> option would be fine).

A question on this though - whilst commitizen does not support dev versions, will it still be able to successfully parse a PEP440-compatible version that includes a dev version, for the sake of bumping? I.e. will commitizen be able to bump 1.0.1.dev0+foo.bar.baz to 1.0.2 or 1.1.0 etc.?

And the ultimate related question - is there any planned support for dev versions?

[jakob-keller]

I would also love to see this feature implemented!

[adamcunnington-gdt]

Thanks. To your last point, you are right, #150 does relate to that. I answered my own question there though - I tried to see if I could bump a PEP440-compatible version to a SemVer-compatible version and that works at least - so I can’t use commitizen to create a .devN+… version, but it can at least read it when it comes to regex replace to bump with a release version.