-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] unpublish from private registry #4331
Comments
I can confirm this bug with npm@8.5.1. I tried it out. It still works with 8.3.0 and stopped working with 8.3.1. |
Closing: This should be resolved as of |
Upgraded to v8.6.0 but this still appears to be an issue for me? |
Upgraded to v8.7.0 and still appears, so it seems |
If this is still an issue for you please open a new issue describing the steps to reproduce. The bug here was that a package's publishConfig was not being applied during unpublish, which was fixed. It's very likely this is a different bug. |
Why is the issue closed? It is still issue. Workaround to unpublish from private registry is:
|
The issue is closed because the bug as reported here was fixed. As I stated in my previous comment if there is something not working for you please open a new issue so we can triage it. There is another open unrelated unpublish issue here for example #5685 |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
When trying to unpublish a package from a private registry, npm looks up from the package in https://registry.npmjs.org.
This is the output from the GitLab pipeline:
Expected Behavior
It should unpublish @foo/bar package from private registry as configured within .npmrc file.
Note: It worked until a week ago (January 18th) using node:latest as pipeline base docker image.
Steps To Reproduce
Environment
The text was updated successfully, but these errors were encountered: