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 fails silently when not authorized #7155
Comments
Still an issue in 1.22.10 on mac os |
Can confirm, this is still an issue for me as well |
I can confirm this is fixed in 1.22.19, however a different problem exists: yarn still increments the semver in my package.json, even when
Note that exit code is 1, but in my package.json, the version field has been updated to 1.0.4. Now, when I revert my package.json and attempt to publish again, Yarn still thinks that version 1.0.4 exists:
This means I can never actually publish version 1.0.4... |
It's not fixed in 1.22.19, unfortunately:
|
Do you want to request a feature or report a bug?
bug
May be related to #6200
What is the current behavior?
When doing a
yarn pbulish
to a private registry (with credentials provided as_auth
within an.npmrc
): If the credentials are invalid, yarn reports an error (when using--verbose
) but still finishes "successfully":Without using
--verbose
the publish process seems to have succeeded and I've been wondering where my package is. Only using verbosity helped me to see that I have not been authorized to the registry.My .npmrc looks like
If the current behavior is a bug, please provide the steps to reproduce.
yarn publish
What is the expected behavior?
Yarn should fail with a) an error telling the user that authorization failed and b) non-zero exit code.
Please mention your node.js, yarn and operating system version.
node version: v10.15.3
yarn version: 1.15.2
OS: Windows 10 with a git bash
The text was updated successfully, but these errors were encountered: