Repository navigation
Push the symbols to NuGet.org only once - #675
Merged
Merged
Conversation
dotnet nuget push already pushes the .snupkg next to each .nupkg, so the separate symbols push got a 409 Conflict and failed the release job.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The NuGet.org release push fails after publishing, because it pushes the symbols package twice.
dotnet nuget push ./nugets/*.nupkgalready pushes the.snupkgnext to each package, so the seconddotnet nuget push ./nugets/*.snupkggets a 409 Conflict ("another copy of this symbols package pending validation"). It first happened releasing Radical.Avalonia 1.0.0 (https://github.com/RadicalFx/Radical.Avalonia/actions/runs/41324545604): the package and its symbols were published, but the job failed.This removes the second push. The Feedz push doesn't change: Feedz accepts the duplicate.