fix: use dotnet nuget to push packages#80
Conversation
This PR modernizes the NuGet package publishing process by replacing the legacy `nuget.exe` tool with the built-in `dotnet nuget` command. This change follows best practices recommended in [Meziantou's blog]((https://www.meziantou.net/publishing-a-nuget-package-following-best-practices-using-github.htm)) for more reliable and streamlined package publishing. **Key changes:** - Replaces `nuget push` with `dotnet nuget push` command using updated parameter syntax - Adds .NET SDK setup to ensure `dotnet` command availability - Updates dotnet-stryker tool version to 4.7.0
There was a problem hiding this comment.
Pull Request Overview
This PR modernizes the NuGet package publishing process by replacing the legacy nuget.exe tool with the built-in dotnet nuget command for more reliable package publishing.
- Updates package publishing command from
nuget pushtodotnet nuget pushwith modernized parameter syntax - Adds .NET SDK setup step to ensure
dotnetcommand availability in the workflow - Updates dotnet-stryker tool to version 4.7.0
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| Pipeline/Build.MutationTests.cs | Updates dotnet-stryker tool version to 4.7.0 |
| .github/workflows/build.yml | Modernizes NuGet publishing by adding .NET SDK setup and replacing nuget.exe with dotnet nuget command |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
🚀 Benchmark ResultsDetails
|
|
This is addressed in release v1.4.0. |



This PR modernizes the NuGet package publishing process by replacing the legacy
nuget.exetool with the built-indotnet nugetcommand. This change follows best practices recommended in Meziantou's blog for more reliable and streamlined package publishing.Key changes:
nuget pushwithdotnet nuget pushcommand using updated parameter syntaxdotnetcommand availability