-
Notifications
You must be signed in to change notification settings - Fork 110
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
fix: use NPM_CONFIG_USERCONFIG
in get-registry to match auth
#362
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sending the pull request!
Can you please add a test to make sure we don't break this behavior in future!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I confirmed locally that the test fails without the fix. Thanks for the PR @jameshartig 👍🏼
NPM_CONFIG_USERCONFIG
in get-registry to match auth
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh sorry, one more thing, I think we should document the env variable in https://github.com/semantic-release/npm#environment-variables?
Previously NPM_CONFIG_USERCONFIG was only used for getting the auth token and not used for actually getting the registry from .npmrc. Fixes semantic-release#349
@gr2m good call! I updated the README |
🎉 This PR is included in version 7.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Previously NPM_CONFIG_USERCONFIG was only used for getting the auth token and not used for actually getting the registry from .npmrc.
Fixes #349