Nuget upload frequently fails

[d4e666]

Select Topic Area

Question

Body

I use a powershell to package and upload my nugets. Most of the time this works perfectly. Sometimes I do see my script running perfecly but my nugets aren't becoming visble in the nuget feed. When I edit the query to go to my nuget specs, I do see the files created, but its not created successfully (I check this by changing some nuget properties and getting the "cannot edit right now" error messge. Why is this failing since I cn't seem to find any logging or other indication of what is going wrong. Yes my nuget names are quite long,but since I don't get a warning or error I don't blame my long names. If this is an issue I blaim the github developer for failing to write proper checks.

[luxetidal]

Intermittent NuGet pushes usually aren’t a packaging bug but an upload/validation/visibility issue in the feed. Things to check quickly:

• Capture the server response: run the push with verbose logging (e.g. nuget/dotnet nuget push with -Verbosity detailed or --verbosity detailed) and save the HTTP status and body. That tells you if the server accepted the file or returned an error that your script is swallowing.
• Watch for conflict/duplicate/version collisions: a 409/409 Conflict or similar means the version already exists (or partial metadata exists) and will make the package non-editable until resolved.
• Processing / indexing delay: many feeds (including GitHub Packages / NuGet hosts) process uploads asynchronously — the package file may be present on storage but the package is still being validated/indexed and won’t be editable/visible until processing completes. Add a short retry/backoff and re-check the package metadata endpoint instead of only checking storage.
• Auth / token scope and transient auth errors: confirm the push token has the correct scope and isn’t intermittently rejected (look for 401/403 responses).
• Feed-side validation failures: malformed nuspec metadata, missing required fields, or invalid characters/length in ID/version can cause silent validation failures. Validate the package locally and compare nuspec metadata against feed limits.
• Check feed/registry logs & status: use package feed UI/audit logs (if available) and the provider’s status page to rule out service incidents or replication delays.

Suggested immediate fixes: enable detailed logging in the push command and capture responses, implement retries with exponential backoff, and add a post-push validation step that queries the feed’s package metadata endpoint (so you fail loudly if processing didn’t complete). These steps will show whether this is client-side, transient network/service behavior, or a feed validation problem.

[Viganop]

Nice

[Viganop]

.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬