increasing next_version 'prerelease' with different prerelease_token

[hokreb]

Situation

I am not shure if this should be seen as a bug or an enhancement. I have observed this behaviour in version 2.13 of semver.

If I have a version 1.2.3

ver = semver.VersionInfo.parse('1.2.3')

and would like to get the next dev Version,
I will get the version 1.2.4-dev.1 by calling

ver_dev1 = ver.next_version('prerelease', prerelease_token='dev')

If I would like to get the next release candidate, I would call

ver_rc1 = ver_dev1.next_version('prerelease', prerelease_token='rc')

which should be 1.2.4-rc.1

but the result is 1.2.4-dev.2

To Reproduce

import semver
ver = semver.VersionInfo.parse('1.2.3')
ver_dev1 = ver.next_version('prerelease', prerelease_token='dev')
ver_rc1 = ver_dev1.next_version('prerelease', prerelease_token='rc')
print(ver_rc1)

The result is

1.2.4-dev.2

Expected Behavior

I would assume, that according to semantic versioning the result should be

1.2.4-rc.1

Environment

• OS: Linux
• Python version 3.6.13
• Version of semver library 2.13

[fleetingbytes]

Similar behavior is also observed with build bumps. A custom build string once set, cannot be reset in a subsequent call of the bump_build method.

[tomschr]

Yes, this is similar to issue #369.

[tomschr]

@hokreb Time flies! Sorry for the delay.

I've tried to confirm it, but if I use the latest version from the master branch, it works:

>>> import semver
>>> ver = semver.VersionInfo.parse('1.2.3')
>>> str(ver.next_version('prerelease', prerelease_token='dev'))
'1.2.4-dev.1'

Can you confirm? If yes, I'd like to close this issue. Thanks!