Print valid cli arguments for [part] in usage string about bumpversion HOT 8 OPEN

Ok, that error is definitely misleading, sorry about that, I'll fix it.

However, you need to specify which part of the version to bump (in the standard configuration that's "major", "minor", "patch"), as in bumpversion [--options] patch to bump the last number.

from bumpversion.

Because I see current_version = 0.5.2.beta in your config:

At the moment bumpversion doesn't support parts (that's what I call the individual digits that are combined to the version number) that don't contain a number, so current_version = 0.5.2.beta1 might work (see these two lines

I'm interested in your workflow (is it 0.5.1 -> 0.5.2.beta -> 0.5.2 -> ... ?) and to make it work in bumpversion, can you go into detail on that ?

from bumpversion.

Also, --config .bumpversion.cfg is the default, so, unless you want to use another config file, it should be safe omit.

from bumpversion.

Thanks for the prompt reply.

Yes, my workflow is 0.5.1 -> 0.5.2.beta -> 0.5.2.RC1 -> 0.5.2 -> ... Although now that I think of it I probably should be doing beta1.

Was patch required before? I suppose it's nice to just not specify the next version but just which part to bump.

from bumpversion.

OK, I tried bumpversion --new-version 0.5.2 patch but that changed the version number to patch?

from bumpversion.

Yes, I usually just use bumpversion patch alone, everything else is in the config file.

OK, I tried bumpversion --new-version 0.5.2 patch but that changed the version number to patch?

That is a bug then, I'll have to look into.

from bumpversion.

I also think:

  part                  Part of the version to be bumped.

In the help docs should list which arguments are possible and their behavior.

I now tried bumpversion patch and it bumped 0.5.2.beta to 0.5.3.

from bumpversion.

You're right, thanks! I'll get to that.

from bumpversion.