I'm confused by test_python_prerelease_release_postrelease(). I think can see why, technically, it behaves the way it does, but I'm not clear on why it's desirable:
It seems odd that if I'm on 1.1 and I increment minor I end up on a prerelease version of 1.2. In this situation, is there any way of getting 'straight' from 1.1 to 1.2, other than specifying '--new-version', or incrementing prerel lots of times?
I think the behaviour I naturally expect would be for 1.1 minor to increment straight to 1.2 and 1.1 prerel to increment to 1.2dev - is there any way of achieving that? Maybe I'm just thinking backwards.
Hi,
I'm confused by
test_python_prerelease_release_postrelease(). I think can see why, technically, it behaves the way it does, but I'm not clear on why it's desirable:https://github.com/peritus/bumpversion/blob/6ec908f018a827bfae94ed50baf241461eba7bcb/tests/test_cli.py#L1335-L1339
It seems odd that if I'm on 1.1 and I increment
minorI end up on a prerelease version of 1.2. In this situation, is there any way of getting 'straight' from 1.1 to 1.2, other than specifying '--new-version', or incrementingprerellots of times?I think the behaviour I naturally expect would be for 1.1
minorto increment straight to 1.2 and 1.1prerelto increment to 1.2dev - is there any way of achieving that? Maybe I'm just thinking backwards.Really appreciating a great tool - thanks!