Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The nuget push command failure is misleading #10314

Open
IEvangelist opened this issue Dec 20, 2024 · 0 comments
Open

The nuget push command failure is misleading #10314

IEvangelist opened this issue Dec 20, 2024 · 0 comments

Comments

@IEvangelist
Copy link

IEvangelist commented Dec 20, 2024

NuGet Product Used

dotnet.exe

Product Version

9.0.100

Worked before?

No response

Impact

It's more difficult to complete my work

Repro Steps & Context

Context:

A few years ago, I wrote some packages that were prefixed with GitHub.* and GitHub has since reserved that prefix. The existing packages that I've maintained are able to be updated, but I'm not able to push new packages with the prefix anymore. I'm good with all that, but I was unaware that the prefix was reserved as the error/failure messages are misleading.

CI/CD

image

You can see that the error message indicates a package with the same ID already exists, which is not true, you can look yourself. But the prefix is now reserved, that should be in the error message.

Something more like the UX on NuGet.org would be better:

image

Reproduce:

Push a package to the official feeds where the package ID includes a prefix that is reserved.

Verbose Logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants