Do you want to request a _feature_ or report a _bug_? Feature
What is the current behavior?
When you enter yarn version it opens up a prompt to enter a new version. This is hard for scripts to deal with.
What is the expected behavior?
The following should create a new version without prompting the user:
yarn version [1.0.0,major,minor,patch,etc]
jamiebuilds
👍1
>All comments
Sorry to dig this up, but this doesn't seem to work without specifying the --new-version flag which is rather annoying. It's so ingrained in me to type npm version patch, why do we need to include this very verbose flag to get the same result with yarn?
Can't the version command check if the parameter passed after the command matches a valid version identifier and update it accordingly, e.g. [1.0.0,major,minor,patch,etc]?
adamreisnz
on 3 Aug 2017
👍9
Was this page helpful?
0 / 5 - 0 ratings
Related issues
NonPolynomial
路
3Comments
danez
路
3Comments
seansfkelley
路
3Comments
victornoel
路
3Comments
yarn check fails if there's no lockfiles, yarn install doesn't generate one without any dependencies
bouk
路
3Comments
Most helpful comment
Sorry to dig this up, but this doesn't seem to work without specifying the
--new-versionflag which is rather annoying. It's so ingrained in me to typenpm version patch, why do we need to include this very verbose flag to get the same result with yarn?Can't the
versioncommand check if the parameter passed after the command matches a valid version identifier and update it accordingly, e.g.[1.0.0,major,minor,patch,etc]?