Publish without version prompt

[binarykitchen]

Do you want to request a feature or report a bug?
minor feature

What is the current behavior?
yarn publish is prompting for a new version number

What is the expected behavior?
For a release and deployment bash script, I bump the new version internally and would like to pass on the new version to yarn with an argument like yarn publish --version new.version.number

And better, yarn publish auto, would parse the new version number in package.json. Sometimes I bump it there too.

Please mention your node.js, yarn and operating system version.
Think that's irrelevant?

[arcanis]

You should be able to run yarn publish --new-version x.y.z to fix the version from the command line. Unfortunately, it seems impossible to just skip the version bump at all. Maybe the current behaviour should be moved inside a -i,--interactive flag ... wdyt, @bestander?

[bestander]

Yeah, we should allow publishing without bump.
Maybe an argument --no-version-bump would be the easiest way to do it without breaking current API.
Send a PR!

[binarykitchen]

but i am confused, code says there is already an argument for version, see
https://github.com/yarnpkg/yarn/blob/master/src/cli/commands/version.js#L70

[bestander]

That one is yarn version command.

[binarykitchen]

@bestander well, the code for the yarn publish command is using it, see https://github.com/yarnpkg/yarn/blob/master/src/cli/commands/publish.js#L138

[bestander]

So what happens when you pass version via --version?

[binarykitchen]

ah, i think we can do yarn publish --new-version x.y.z ... will try tonight

[binarykitchen]

hmm, tried that and am hitting the next stumbling block. with --new-version i see this error

yarn publish v0.22.0
info Current version: 1.25.7
error New version is the same as the current version.
info Visit https://yarnpkg.com/en/docs/cli/publish for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

let me explain my use case. i am running this bash script to deploy new releases:
https://github.com/binarykitchen/videomail-client/blob/develop/bin/release.sh

there you can see that i am tagging new releases with git flow, doing stuff on gulp, bumping the version, doing a final commit before pushing and publishing that to npm. in other words, the version bump already has been done and i don't want yarn to bump it.

honestly i think yarn shouldn't do this local check and not print the New version is the same as the current version. error. leave it to npm to respond with an error when the version already exist.

[binarykitchen]

@bestander @arcanis if you think that's a separate issue, happy to raise another one

[bestander]

Go ahead, a PR will be appreciated

…

On Sat, 8 Apr 2017 at 02:24, Michael Heuberger ***@***.***> wrote: @bestander <https://github.com/bestander> @arcanis <https://github.com/arcanis> if you think that's a separate issue, happy to raise another one — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3011 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACBdWIgyC3S26pih2d_Mo4mwCCUZVU45ks5rtuHkgaJpZM4Msop0> .

[binarykitchen]

here's the PR @bestander #3103

[bestander]

fixed

[binarykitchen]

@bestander is this still not out?

[bestander]

It is in branch 0.24

We just keep it as RC till tomorrow but you can install it anyway.