Yarn silently fails to publish package

[mlewando]

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

bug

What is the current behavior?

During yarn publish execution I had the wrong configuration in .npmrc file. The auth token was specified as _authToken=TOKEN. With this configuration, yarn happily said that the package was published, but in reality, it was not.

Some additional information:

I have private nexus repository specified in package.json in publishConfig.registry. From the verbose logs and debugging I know that yarn used this configuration (but. eg. publishConfig.tag is ignored).

When I removed the token from .npmrc, publish failed on authentication - this was correct behavior.

When I changed _authToken=TOKEN to _auth=TOKEN it correctly published the package.

I'm not 100% sure if this is nexus or yarn problem yet.

If the current behavior is a bug, please provide the steps to reproduce.

Try to publish any package to nexus (I'm not 100% sure if this needs to be nexus) with auth token specified in .npmrc file as _authToken=TOKEN.

What is the expected behavior?

yarn publish should fail when the publish operation is not successful

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

Node: 8.11.3
OS: Windows 10 x64
yarn: 1.9.2

[stickycode]

@torifat its been a while, isn't this issue quite important for build automation, I would have expected some impetus to get it sorted