Provide prerelease option for version-resolver

[Happypig375]

With patch, the next version after 0.5.0-alpha would be 0.5.1.
However, with Semantic Versioning, the next resolved version should actually be 0.5.0.
Please add this option.

[jetersen]

Not sure how you would achieve that within semver. I think their logic is correct after a prerelease the next version is an release.

inc(v, release): Return the version incremented by the release type (major, premajor, minor, preminor, patch, prepatch, or prerelease), or null if it's not valid
premajor in one call will bump the version up to the next major version and down to a prerelease of that major version. preminor, and prepatch work the same way.
If called from a non-prerelease version, the prerelease will work the same as prepatch. It increments the patch version, then makes a prerelease. If the input version is already a prerelease it simply increments it.

atm we are simply passing major, minor, or patch

[Happypig375]

Should we allow all these options or just prerelease?

[afirth]

I'm also wondering how to do this inside this tool.
Our workflow
master -> dev
0.1.1-rc1 -> int
0.1.1 -> production

I would like master commits to draft an RC, incrementing the RC number if a tag at the same major.minor.patch already exists.

[Nuru]

I would like to see a combined prerelease/release candidate option. This could be done as an extension to version-resolver. Add another set of labels that indicate release candidate. Logic something like this:

This PR has a release candidate tag:

• Mark the release as a prerelease
• Was the previous release a semver ending with -rc\d+?
  • yes: take the previous release tag, increment the number after -rc, use that for the new release tag
  • no: compute the next release version according to the other tags, append -rc1 to it, use that for the release tag

This PR does not have a release candidate tag:

• Was the previous release a semver ending with -rc\d+?
  • yes: take the previous release tag, remove -rc and everything after it, use that for the new release tag
  • no: compute the next release version according to the other tags

[brian-pickens]

Throwing my hat in the ring here for this feature.

[neilime]

I've made a pull request for this: #1303