npm access token alowed IP ranges field doesn’t support IPv6 CIDR ranges #186022
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
The Allowed IP Ranges field when creating a token (see https://docs.npmjs.com/creating-and-viewing-access-tokens) doesn’t support IPv6 CIDR ranges. This means that, if I’m publishing from an IPv6-enabled environment, I effectively can’t use allowed IP ranges at all, because it doesn’t seem to be possible to force
npm publishto use IPv4 only.Beta Was this translation helpful? Give feedback.
All reactions