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

AspNetCore.HealthChecks.Rabbitmq.v6 nuget package wasn't released #2358

Open
eerhardt opened this issue Jan 2, 2025 · 6 comments
Open

AspNetCore.HealthChecks.Rabbitmq.v6 nuget package wasn't released #2358

eerhardt opened this issue Jan 2, 2025 · 6 comments

Comments

@eerhardt
Copy link
Collaborator

eerhardt commented Jan 2, 2025

As part of the 9.0 release, the new AspNetCore.HealthChecks.Rabbitmq.v6 package wasn't released on nuget.org:

https://www.nuget.org/packages/AspNetCore.HealthChecks.Rabbitmq has a 9.0.0 version

https://www.nuget.org/packages/AspNetCore.HealthChecks.Rabbitmq.v6 doesn't exist

@unaizorrilla @adamsitnik

@Alirexaa
Copy link
Collaborator

Alirexaa commented Jan 3, 2025

@adamsitnik
Copy link
Collaborator

I've pinged @unaizorrilla offline

@unaizorrilla
Copy link
Collaborator

Working on it!!

@unaizorrilla
Copy link
Collaborator

Hi again

@adamsitnik @Alirexaa

After some debug on the actions and some local actions the response on push package is on conflict because package already exist, (non sense because not exist) but with detailed information the real reason is because the name "was reserved"

Package 'xxx.\artifacts\AspNetCore.HealthChecks.Qdrant.9.0.1.nupkg' already exists at feed 'https://www.nuget.org/api/v2/package'.
The package ID is reserved. You can upload your package with a different package ID. Reach out to [email protected] if you have questions.

Let me do some investigations or @adamsitnik if you can point to some people at NuGet for more information will be good!

@adamsitnik
Copy link
Collaborator

I am searching offline for somebody from the NuGet Team that could help us.

@eerhardt
Copy link
Collaborator Author

Might be a dumb question, but have you tried contacting [email protected]?

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

No branches or pull requests

4 participants