Closed blairlearn closed 1 year ago
This appears to be related to the update of the setup-dotnet
action from v1
to v3
which was done as part of #47.
In v1
of the action, the dotnet nuget push ./*.nupkg
command results in only the binary code package being published. In v3
, the symbols package is also published. GitHub treats this as a duplicate, causing the upload to fail.
It's not clear that GitHub can function as a symbol server (and debugging into a NuGet package is something of a dark art). For now, the best solution seems to be preventing the symbols package from being generated.
Fixed (or addressed anyhow) in 96b3c761712f8f64ffdf37f2ca4fdbeec30abbaa
Issue description
During the build for the v2.x branch, pushing the NuGet package fails.
Steps to reproduce the issue
What's the expected result?
What's the actual result?
Additional details / screenshot
Related Tickets