New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yarn publish in a script requires user interaction #2445
Comments
I too would like to have a way to publish on npm using yarn, I already manage the version number bump in my scripts. As a side note, |
Carrying on the conversation from #722,
|
Related to #2430 |
Closing as a dup of #610 since the longer conversation is held there. |
This is really annoying. Generally we want to use `yarn` instead of `npm`. However, when running `lerna publish`, if it uses `yarn publish` that command will try to prompt the user for a version number, which breaks when running from the lerna script. See yarnpkg/yarn#2445 for details. Can't really find any other reports of the issue, especially from the `lerna` side of things.
@rally25rs I don't see any mention of this particular problem ( |
@lehni the original post states
which is mentioned in comment #610 (comment) which is why I closed it as a duplicate. If you could add a comment to #610 for the password issue, it would be helpful. Thanks! |
yarn publish
(0.18.1, node 6.3.1, Windows) is no drop in replacement fornpm publish
when used in a script: Using an auth token in my.npmrc
,npm publish
runs without user interaction,yarn publish
asks for a new version number. It would be greate to have a way to publish without interaction.To answer the questions not yet asked: It's our in house sinopia and publishing is restricted to our build bot. Therefore the new version number is always checked in before publishing.
The text was updated successfully, but these errors were encountered: