Github packages broken for a repository

[ribull]

Select Topic Area

Bug

Body

I'm using a Github action across 12 different repositories that builds a nuget package, then pushes it to my organizations github packages. In 11 of those repositories the action works perfectly, however in the 12th it:

1. Is a repository in the same organization as all the others
2. Has the same GH Token (provided by Github) as the others
3. Has the same permissions, and no variables or secrets
4. Is running the exact same code as the other 11 (it's executing literally the same github action with an action that simply calls the other one)
5. (Importantly) It fails to push to github packages and gives an unauthorized error.

This forced me to resort to manually building, packing, and pushing to the github packages nuget registry via my own computer with my own authentication token (which has been working to pull these packages from github packages for months) and that has worked for the last two weeks.

However, yesterday I built, packed, and pushed the package to packages via my own computer and was unable to pull the most recent version from packages via nuget. It was there, I could see it in the web interface as a package that existed, but despite checking the registry many times over an hour it never appeared as an option to pull (as I have done literally hundreds of times before in my dotnet projects that have dependencies in my organizations packages registry).

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