yarn version not working as stated in docs?
#2491
Comments
|
Upgraded from |
|
Also seeing this today after upgrading from 0.18.1 to 0.19.1. node: v7.2.1 0.18.1 still works as expected after downgrade. |
|
cc @bestander - Sounds like a regression in 0.19.x. |
|
Created an issue to track cherry-picks #2499. |
…rnpkg#2491) There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. This relates to PR yarnpkg#2268.
…g#2491) There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. This relates to PR yarnpkg#2268.
There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. This relates to PR yarnpkg#2268.
There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. In other words, executing the command `yarn version` would yield the same output as `yarn --version`. This relates to PR yarnpkg#2268.
…pkg#2491) There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. In other words, executing the command `yarn version` would yield the same output as `yarn --version`. This relates to PR yarnpkg#2268.
|
Same here. The upgrade to 0.19 simply outputs the yarn version now, instead of tagging a new version. |
|
Since it's a regression, |
…pkg#2491) There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. In other words, executing the command `yarn version` would yield the same output as `yarn --version`. This relates to PR yarnpkg#2268.
…pkg#2491) There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. In other words, executing the command `yarn version` would yield the same output as `yarn --version`. This relates to PR yarnpkg#2268.
|
This is probably not the correct place to ask this, but Is there a way to rollback to an older version? I can't find a way to do it through |
|
@danny-andrews Google returned this question on StackOverflow, maybe it'll be useful for you: https://stackoverflow.com/questions/3987683/homebrew-install-specific-version-of-formula. I don't have a Mac any more so I can't test it though. Alternatively, all the other methods of installing Yarn let you specify the version. If you use the installation script, you can pass a |
|
Yeah, I went through all those, but they don't seem to be valid anymore. I reverted to installing via |
… (#2510) * Fix `yarn version` which yields same output as `yarn --version` (#2491) There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. In other words, executing the command `yarn version` would yield the same output as `yarn --version`. This relates to PR #2268. * Shift first arg that shares name with an option to circumvent conflicting name bug Relating to tj/commander.js#346, when an arg shares the same name as an option, it wrongly ignores the arg command and executes the option instead. Therefore, executing 'yarn version' would instead translate to 'yarn --version'. This logic can subsequently be removed once this issue is resolved.
… (#2510) * Fix `yarn version` which yields same output as `yarn --version` (#2491) There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. In other words, executing the command `yarn version` would yield the same output as `yarn --version`. This relates to PR #2268. * Shift first arg that shares name with an option to circumvent conflicting name bug Relating to tj/commander.js#346, when an arg shares the same name as an option, it wrongly ignores the arg command and executes the option instead. Therefore, executing 'yarn version' would instead translate to 'yarn --version'. This logic can subsequently be removed once this issue is resolved.
… (#2510) * Fix `yarn version` which yields same output as `yarn --version` (#2491) There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. In other words, executing the command `yarn version` would yield the same output as `yarn --version`. This relates to PR #2268. * Shift first arg that shares name with an option to circumvent conflicting name bug Relating to tj/commander.js#346, when an arg shares the same name as an option, it wrongly ignores the arg command and executes the option instead. Therefore, executing 'yarn version' would instead translate to 'yarn --version'. This logic can subsequently be removed once this issue is resolved.
|
Fix will be released in 0.20.1 |
…pkg#2491) (yarnpkg#2510) * Fix `yarn version` which yields same output as `yarn --version` (yarnpkg#2491) There was a conflict when commander attempts to parse the incoming args between the command executed and the options since the name `version` was shared. In other words, executing the command `yarn version` would yield the same output as `yarn --version`. This relates to PR yarnpkg#2268. * Shift first arg that shares name with an option to circumvent conflicting name bug Relating to tj/commander.js#346, when an arg shares the same name as an option, it wrongly ignores the arg command and executes the option instead. Therefore, executing 'yarn version' would instead translate to 'yarn --version'. This logic can subsequently be removed once this issue is resolved.
|
Sorry to comment on an old issue, but I think there's still a problem with the backwards compatibility of the yarn |
|
I think there was a conscious choice to split |
|
@markmsmith Did you ever pursue that? We're also looking to replace npm with yarn and are a bit surprised at how limited |
|
Interested in this as well, |
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
yarn versionreturns the current version of yarn similar to the commandyarn --version.If the current behavior is a bug, please provide the steps to reproduce.
Run the command
yarn versionin your CLI.What is the expected behavior?
Unless I'm misinformed, should it not be performing the behavior described in the docs? https://yarnpkg.com/en/docs/cli/version
Running
yarn versionshould output something like the following:Please mention your node.js, yarn and operating system version.
node: 7.4.0
yarn: 0.19.1
os: macOS 10.11.6
The text was updated successfully, but these errors were encountered: