release-as isn't working as expected and the version isn't matching the conventional commit messages

[pabloleone]

There you can see that the command is not outputting the version specified in release-as, if I remove the option it works though.

How is it possible? If the new version contains changes, then a minor version should be created instead of a patch, as far as I know. The system is detecting the features but still versioning the app using a new patch version.

Any help? I might be missing something.

I'm using the conventional commit plugin for VSCode to write the commits.

[burgerni10]

I had a similar issue using --prerelease AND --release-as. What I noticed is the following (assuming my project is in version 1.0.0)

-standard-version -i CHANGELOG.md --prerelease alpha --release-as 4.2.3 will fail (version null)
-standard-version -i CHANGELOG.md --prerelease alpha --release-as patch will succeed with v1.0.1-alpha (you can use minor or major in a similar way)
-standard-version -i CHANGELOG.md --release-as 4.2.3 will succeed with v4.2.3

The mix of prerelease and release-as seems to be the problem, but I think it's the expected behaviour since prerelease is not a release. So I'm not sure it's a "bug" but I just use standard-version so I'm not the one to decide what is the expected behaviour of the package !