-
Notifications
You must be signed in to change notification settings - Fork 113
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
Broken verify-auth
implementation
#414
Comments
antongolub
added a commit
to antongolub-forks/semantic-release-npm
that referenced
this issue
Oct 27, 2021
antongolub
added a commit
to antongolub-forks/semantic-release-npm
that referenced
this issue
Oct 27, 2021
antongolub
added a commit
to antongolub-forks/semantic-release-npm
that referenced
this issue
Oct 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR: I receive
ENEEDAUTH
npm errors until I comment out these three lines in my node_modules directory -- then publication works fine.What I did
I attempted to use multi-semantic-release to semantically-publish the typescript-tools monorepo. I configured the
NPM_TOKEN
environment variable with an Automation-type npm tokenBoth locally and in GitHub actions I invoked
What I expected to happen
I expected packages to publish semantically.
What actually happened
I received the npm error
More details
Note: I originally opened an issue in multi-semantic-release but determined the root cause did not lie with code in that repository.
I have 24 packages in the typescript-tools monorepo. While instrumenting the @semantic-release/npm code with debug statements I learned that some (but not all!) of the
npm whoami
calls in this try block were failing. Plenty of them succeeded in printing my npm username in my stdout.I was sure from my debugging that the npm credentials were being configured in the temporary
.npmrc
file correctly, so I tried commenting out thethrow
statement handling thewhoami
errors and sure enough, I was able to publish!So something must be going wrong with the
whoami
check. I don't think it's being rate-limited; I tried making 100 parallel calls tonpm whoami
using the @semantic-release/npm temporary.npmrc
configuration and all 100 calls succeeded.The text was updated successfully, but these errors were encountered: