GitHub RubyGems server is broken and cannot install recently published packages

[smdern]

Select Topic Area

Bug

Body

We have many private Ruby gems in GitHub packages. Yesterday, we discovered that newly published gems are not showing up in the RubyGems registry for accounts that have repository read, write, and admin permissions. But an account with organization admin permissions was able to install the packages fine.

Promoting an account to org admin allowed an account to install a package and then removing org admin permissions from that account still allowed the user to download the package (that account always had repository admin permissions).

It appears that the registry isn't respecting the repository's permissions and accounts that have read permission for a package aren't able to install the package.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[smdern]

It looks like the rubygems.pkg.github.com/<org>/versions endpoint doesn't include the package, but rubygems.pkg.github.com/<org>/info/<package-name> endpoint shows that the package exists.

[smdern]

It appears that the versions endpoint will not include more than 500 packages. Deleting some packages ended up allowing the newly published packages to be included in the list. A package limit is surprising and I could not find any documentation regarding a limit.

[aaronjensen]

Furthermore, that package limit does not apply to admins of the organization, which is even more confounding.