Fetching package from private Rubygems Registry errors on checksum mismatch #147180
Replies: 4 comments
-
💬 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.
-
Using |
Beta Was this translation helpful? Give feedback.
-
Deleting an old previous package seems to also get it to work again with just Not sure if this means that our index was just too long or full??? Or we might have triggered the checksums to be recalculated by deleting an old package? Not too sure. |
Beta Was this translation helpful? Give feedback.
-
One of my colleagues have raised a request with Github Support to get some more answers. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Getting an error when pulling in Rubygems package from private rubygems registry:
https://rubygems.pkg.github.com/<org_name>
Similar to:
Beta Was this translation helpful? Give feedback.
All reactions