bump_prerelease and bump_build return smaller version

The current behavior of bump_prerelease and bump_build seems wrong, or at least unexpected:

In [64]: v1 = semver.parse_version_info('0.1.4')                                                                                              

In [65]: v1 < v1.bump_major()  # good
Out[65]: True

In [66]: v1 < v1.bump_minor()  # good                                                                                                               
Out[66]: True

In [67]: v1 < v1.bump_patch()  # good                                                                                                    
Out[67]: True

In [68]: v1 < v1.bump_prerelease()   # not good                                                                                                       
Out[68]: False

In [69]: v1 < v1.bump_build()  # not good                                                                                                    
Out[69]: False

Is this deliberate? I would expect them to return what v1.bump_patch().bump_prerelease() and v1.bump_patch().bump_build() return now.

[gsakkis]

@tomschr thanks for taking the time to come up with a draft, I’ll take a look at it! The signature looks good, I agree that build is less important and clear; we can always extend it later if necessary.

[gsakkis]

@tomschr The only other library I checked is python-semanticversion which doesn’t currently provide a method to bump prerelease (or build); I opened an issue for it.

Among the options you listed I’d be in favor of 4, though not specifically for the build part but all of them. A possible signature could be:

def next_version(version, part, *, prerelease_token="rc", build_token="build"):

where part can be one of {"major", "minor", "patch", "prerelease", "build }.

By the way, the 0.1.4→0.1.5-rc.1 transition isn’t the only problematic one:

In [9]: semver.bump_patch("1.2.4-rc3")                                                                                                                                    
Out[9]: '1.2.5'

I would expect that the next patch version of 1.2.4-rc3 is 1.2.4, not 1.2.5.

So currently there are two special cases, without even considering the build part.