Feature/add preid param for semver

Issue to discuss #83

The idea is to allow adding identifiers to certain tags upon release such as beta, dev, rc, etc.

The proposed command would be:

standard-version -p --tag="<identifier>"

So that running standard-version -p --tag="special-release" would result in a tag something like 2.0.0-special-release.0. Using the prelease command -p repeatedly on the same semver version results in an increment to the last number in the series. So running that previous command again would result in 2.0.0-special-release.1

[bcoe]

Hello all, sorry for being AWOL; npm, IstanbulJS, and yargs have all been quite busy lately and I’ve been spread a bit too thin.

Regarding incrementing logic:

I like this approach a lot as a start @AntJanus:

So running that previous command again would result in 2.0.0-special-release.1

Regarding named major releases:

Regarding named major releases, I’m inclined to keep that discussion out of this thread; not that it’s not a feature we should consider, but mainly it feels like a different set of concerns.

Changelogs

One standing question I have, is what does the changelog look like for pre-release versions, my preference would be having an Upcoming section in the CHANGELOG.md; that would then become the next release, once a non-pre-release version is released. How do folks feel about this? I wonder how hard this would be to pull off.

[bcoe]

@Tapppi @AntJanus I agree, I’ve been using the new --prerelease and --release-as functionality, and I believe it does a good job of hitting an 80/20 with regards to cutting special releases.

Let’s move any further discussion about pre-release improvements to #146.