As a replacement of npm version, there is no control with the version?

[e-cloud]

npm version allows me to control the version to be a major/minor/patch release.

But standard-version just bump the major version part, like v1.2.0 => v2.0.0

[stevemao]

duplicate of #84?

[Tapppi]

@e-cloud That is the point of standard-version though. It analyzes your commit messages and bumps accordingly. Is your issue with the basic functionality or a specific version that is being bumped incorrectly? Although #84 is nice, and should probably be supported 😄

[ggranum]

@Tapppi Not really usable without ability to specify the granularity of the bumps. I can't rev my primary version every time I add a breaking change to master. I'll be on version 42.12.0 before I even issue a beta :~)

[e-cloud]

The basic is right, but i need to do some thing like prerelease(#105 #83). The conventional-recommended-bump can't control that.

[Tapppi]

@ggranum @e-cloud So this is a combination of #83 and #84? #83 should make it possible to do pre-releases and #84 is just a previous issue on the releaseAs option. We can close this as a duplicate and move the discussion there?

[stevemao]

reopen if anyone disagree :)