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
[rush] Cannot publish: getting ENEEDAUTH even though I'm already authenticated #4671
Comments
Which Can you try setting the credentials as an environment variable, referenced in the |
The credentials were already in As a workaround, I ended up writing a small tool that simulates what rush-pnpm does: it iterates over the directories of packages, copies |
Summary
I'm trying to publish monorepo packages to an Artifactory npm registry, but no matter what I try, I get an error about being unauthenticated, even though I'm already authenticated.
Repro steps
Details
It doesn't matter if I use
npm login
and specify the username/password on the command line, or if I store the auth token inside.npmrc
. Same result either way.Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/rush
globally installed version?rushVersion
from rush.json?node -v
)?The text was updated successfully, but these errors were encountered: