NuGet package not visible in organization page after push

[rlos-dev]

Select Topic Area

Bug

Body

Hello everyone,

I recently pushed a NuGet package to a GitHub organization using the dotnet nuget push command, but I'm encountering an issue where the package is not appearing in the expected places.

• While I can see the package on its individual page (e.g., https://github.com/orgs/{org_name}/packages/nuget/package/{package_name}), it does not show up on the organization’s main NuGet package list (https://github.com/orgs/{org_name}/packages?ecosystem=nuget&visibility=all).
• Additionally, when I attempt to change the package visibility to "public", I receive a 404 error when using the command line. From the package page itself, I get the error message: "The package could not be updated. Please try again later".
• The package is also not visible in Visual Studio’s "Manage NuGet Packages" page. Despite selecting the correct source and reloading the package list, it doesn’t appear.
• I’ve tried deleting and re-pushing the package, but it doesn’t resolve the problem.
• In the organization's audit log, I can see my operations (except for the visibility change) as follows: packages.package_version_published, packages.package_published, packages.package_version_deleted.

Has anyone faced a similar issue or have suggestions on how to resolve this? Any help would be greatly appreciated!

Thanks!

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

[Ji993]

We have the same issue.

• When I push npm packages they show up in the packages page - https://github.com/orgs/{org_name}/packages
• When I push nuget packages with the dotnet nuget push command they are NOT visible in the packages page - https://github.com/orgs/{org_name}/packages. The only way to see them is to write the full URL in the browser https://github.com/orgs/{org_name}/packages/nuget/package/{package_name}

Packages should be separate from a repository. We have multiple repositories that use the same nuget package, I don't want to upload a package multiple times to each repository that needs it. Here is a stack overflow link about people having similar issues, but for npm.