Not possible to publish without version bumping

[adamscybot]

Do you want to request a feature or report a bug?
Feature (though this could be argued to be a bug).

What is the current behavior?

Currently, if you are in --non-interactive mode, you can specify a version using the --new-version [version] flag. However, you can not leave this blank.

What is the expected behavior?

I am in a CI scenario where I do not want any version bumping at all. The version currently in the package.json should be taken as good to go. I believe this is the default behaviour on NPM.

Currently it is impossible to use Yarn to publish in this way. I would like to be able to not pass a --disable-version-bump flag to publish so that this behaviour can be achieved.

The option has been discussed before in #3011 (with a hint by @bestander that we should have this) but the issue was ultimately closed with a PR solving a different problem.

Please mention your node.js, yarn and operating system version.

OSX 10.13
Node 8.9.0
Yarn 1.5.1

[peijiesim]

I'm actually a little confused. When I try running yarn publish --non-interactive --new-version [version], I get error No token found and can't prompt for login when running with --non-interactive. Is this not the intended behavior? Also, does running in non-interactive mean that we're skipping over the username and password prompts?

[adamscybot]

@peijiesim This is unrelated to this issue but yes, in non interactive its impossible to prompt for user input...as that would be "interactive". In this mode, its impossible to prompt a user to provide those details. You need to set the token in the .yarnrc file on the machine. If you run "yarn logon" just once on the machine and log in, that will be done for you. From that point on, you can use non-interactive as it will use previous logon details.

[peijiesim]

I'll be working on this.

[maciej-gurban]

@peijiesim Would be great if you could!

[adamscybot]

Im closing this because it was fixed in #5748, thanks @peijiesim !