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.

[bjoerntx]

This helped a lot!

[onetsmr]

I had the same issue. I was pushing 4 libs - 2 ok, 2 missed on the packages tab, but available by direct link (and can't change visibility - some error).
I re-created personal access tokens (classic) with all rights - works.
I re-created token with repo, delete:packages, write:packages (as was) - works.

So, I can conclude that the token was glitching, re-creating it helped me.

[rlos-dev]

Hello everyone,

I wanted to provide an update on the issue I was experiencing with the NuGet package visibility in our GitHub organization.

After some troubleshooting, I found a solution that resolved the problem:

• Initially, I replaced the GitHub token with my personal access token (PAT) when pushing the package.
• Subsequently, I reverted to using the original GitHub token.

This approach restored the package's visibility, aligning with the suggestion provided by @onetsmr.

Thank you all for your assistance and suggestions!

[Knar33]

I am having this issue and re-creating the token twice hasn't resolved it. I can see the package if I navigate to the specific URL but it doesn't show up in the packages tab of my organization. I am admin of the package and owner of the organization.

I am creating a classic PAT with package:read, package:write, and the full repo scope (and even tried enabling all scopes).

[pplaissy]

same issue. Package not visible in the packages page after successfull push.
@Knar33 fix worked for me.

I don't know if it matters here but my pkg doesn't have the same name as my repo.

[MattWalker414]

What project file? Do you mean the .nuspec file used to create the package? Unfortunately, my package is organizational and not tied to a repository.

What worked for me is, manually add the package to a project's packages.json file. Then, open the project in Visual Studio and uninstall the package listed as installed in Nuget Package Manager. At that point, I am able to see the package in Visual Studio and listed in the online Github console.

[Knar33]

What project file? Do you mean the .nuspec file used to create the package? Unfortunately, my package is organizational and not tied to a repository.

What worked for me is, manually add the package to a project's packages.json file. Then, open the project in Visual Studio and uninstall the package listed as installed in Nuget Package Manager. At that point, I am able to see the package in Visual Studio and listed in the online Github console.

Sorry I meant the .csproj file

[vmahilevskyi]

@Knar33 Adding RepositoryUrl property into .csproj file helped to resolve the issue. Thanks.

[adobrzyc]

Thanks, @Knar33, for the workaround! It's worth noting that it only worked for me when the package and repository names matched in case sensitivity. For example, 'Package' didn't work, but 'package' did.

[brinkdinges]

I've also been through the motions today. I tripped a bunch of times, so these hints might be useful to others;

• I first spelled the company name wrong, forgot that there was a dash
• I got an error saying I was over the company budget. I was not allowed to publish until I added a payment method to my free company account, even though the package feature is free.
• I was able to push, but the package only appeared when you entered the full url, like the topic starter experienced. This happened when I let the CLI use the personal access token in my NuGet.config and I didn't include the --api-key argument.
• It only worked when I explicitly added my token when calling "dotnet nuget push" with the --api-key argument. Only this change made the package show up on the company packages page and in Visual Studio.

[tom600x]

I was working with a customer and had the same issue. nuget.exe push was pushing the package but not showing up in the packages area , it did show up with the url https://github.com/orgs/{org}/packages/nuget/package/{package name}. What worked for us was using the dotnet push command with the apikey: dotnet nuget push foo.nupkg -k {api key} -s {source}

[bl2099481]

Had the same issue using dotnet nuget push "*.nupkg" --api-key <key> --source <source> to push multiple packages from one repo. The command would succeed for both packages, but only one would appear in the packages tab at the organization level.

I manually navigated to the package page by building the url https://github.com/orgs/{owner}/packages/nuget/package/{packagename} and clicked the "Add Repository" button to connect it to the repository it was being published from. This caused the package to finally appear in the packages tab.

[Spacefish]

Same thing for us... Guess it´s a bug in GitHub.. Literally pushed 6 packages from CI, 2 of them showed up after a while, 4 not, but you can still pull them / access them via the absolute URL..

Guess the indexing in the list is asynchronous and somehow the jobs fail on GitHubs side for some unknown reason..