Currently, only test cases are added. Will need to find some time to wrap it up. Feel free to take over if anyone's interested in it 🙂

I think this one would be a bit tricky 🤔 prerelease can be anything for semver. Thus, bump prerelease might not make sense to semver. e.g., what should be the next version of 1.1.0-test @woile @noirbizarre WDYT?

I completely missed this. I don't know the answer, but I think we could stick to adding the 0 at the end (?)

1.1.0-test.0
1.1.0-test.1
1.1.0-test.2

Similar to semver:

1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1

And we could assume anything unknown is before alpha (?)

I completely missed this. I don't know the answer, but I think we could stick to adding the 0 at the end (?)

1.1.0-test.0
1.1.0-test.1
1.1.0-test.2

Similar to semver:

1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1

And we could assume anything unknown is before alpha (?)

Sounds like a good idea 🤔 I'll get back to this one when I have more bandwidth

I completely missed this. I don't know the answer, but I think we could stick to adding the 0 at the end (?)

1.1.0-test.0
1.1.0-test.1
1.1.0-test.2

Similar to semver:

1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1

And we could assume anything unknown is before alpha (?)

Perhaps this could be done by having the user configure a prerelease word list and bump to the next item in the list. If the current prerelease is already the last word, upgrade the previous patch version.
In the case where the user has not given a word list, ignore prerelease, and retain any subsequent text after 1.0.0- as is (Behavior consistent with only one word in the word list) ?

e.g.:

with prerelease config:

prerelease = ["test", "beta", "anyword"]
1.0.0-test < 1.0.0-beta < 1.0.0-anyword < 1.0.1-test

no prerelease config:

1.0.0-test < 1.0.1-test < 1.0.2-test

Sounds like a valid idea 👀