Wildcard in "dotnet nuget push" (Windows/Ubuntu)

[carsten-riedel]

Describe the bug

On Windows and Linux, the behavior of using wildcards with the dotnet nuget push [source] command differs.

To Reproduce

Ubuntu

Works on ubuntu 22.04 dotnet version 8.0.203

dotnet nuget push "src/Projects/PackageName/bin/Pack/PackageName.*.nupkg" --api-key $SECRET --source https://api.nuget.org/v3/index.json

Pushing PackageName.0.1.8842.15630.nupkg to 'https://www.nuget.org/api/v2/package'...
  PUT https://www.nuget.org/api/v2/package/
  Created https://www.nuget.org/api/v2/package/ 636ms
Your package was pushed.

Windows

Does not work on windows10 dotnet version 8.0.203

dotnet nuget push "src/Projects/PackageName/bin/Pack/PackageName.*.nupkg" --api-key $SECRET --source https://api.nuget.org/v3/index.json

Results in error

error: File does not exist (src/Projects/PackageName/bin/Pack/PackageName.*.nupkg).

Note

I had one package in the directory src/Projects/PackageName/bin/Pack/

[dotnet-policy-service]

Thanks for creating this issue! We believe this issue is related to NuGet tooling, which is maintained by the NuGet team. Thus, we closed this one and encourage you to raise this issue in the NuGet repository instead. Don’t forget to check out NuGet’s contributing guide before submitting an issue!

If you believe this issue was closed out of error, please comment to let us know.

Happy Coding!

[Kebechet]

NuGet/Home#9390

[Kebechet]

Workaround for windows
You must use Windows-like slashes \ instead of linux-like /
nuget push seems to be very sensitive to this

So in your case

dotnet nuget push "src\Projects\PackageName\bin\Pack\PackageName.*.nupkg" --api-key $SECRET --source https://api.nuget.org/v3/index.json