Don't bump a part if a parent part has its 'final' ('production') value

bump2version 0.5.11

Here’s my config:

[bumpversion]
current_version = 0.2.0
parse = (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(\-(?P<suffix>[a-z]+))?(\.(?P<build>\d+))?
serialize = 
	{major}.{minor}.{patch}-{suffix}.{build}
	{major}.{minor}.{patch}-{suffix}
	{major}.{minor}.{patch}

[bumpversion:part:suffix]
optional_value = prod
values = 
	dev
	prod

[bumpversion:file:VERSION]

If I try to run bumpversion build it will result in 0.2.0-0.1 which it should not. It should throw error similar to the suffix part (ValueError: The part has already the maximum value among...)

bumpversion part	current_version	new_version	works correctly?
build	0.1.0-dev	0.1.0-dev.1	✅yes
suffix	0.1.0-dev.1	0.1.0	✅yes
minor	0.1.0	0.2.0-dev	✅yes
build	0.2.0-dev	0.2.0-dev.1	✅yes
suffix	0.2.0-dev.1	0.2.0	✅yes
build	0.2.0	0.2.0-0.1	❌ should throw error
suffix	0.2.0-0.1	n/a	❌throws ValueError: The part has already the maximum value among ['dev', 'prod'] and cannot be bumped., should throw regex mismatch error
build	0.2.0-0.1	0.2.0-0.1	❌ should throw regex mismatch error

Also checked my regex, it works properly https://regexr.com/4rqaj

[florisla]

I understand your use case now.

The behaviour you want could be implemented as an optional feature in a [part:name] section.

[n3tn0de]

Semver generally concerns releases, not commits, but I see your reasoning.

But this usually solved one way or another with develop/feature branches and/or CI/CD tools, for example, by adding branch name and commit hash to version string in compiled files, if commit doesn’t have a tag and/or not in the master branch.

Anyway, I think we went off topic on this.

Bumping build part on prod should either result in error, 0.2.0-dev.1 or 0.2.0-dev to comply with the scheme.