fix: use dotnet nuget to push packages
#827
Merged
Conversation
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
Try the solution suggested [in meziantou's blog](https://www.meziantou.net/publishing-a-nuget-package-following-best-practices-using-github.htm) to publish nuget packages.
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. This change follows best practices recommended in Meziantou's blog for more reliable and streamlined package publishing.
Key changes:
- Replaces
nuget/setup-nuget@v2action withactions/setup-dotnet@v4for both pre-release and release publishing jobs - Updates push commands from
nuget pushtodotnet nuget pushwith updated parameter syntax
|
|
This is addressed in release v4.3.0. |
This was referenced Aug 15, 2025
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.
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/setup-nuget@v2action withactions/setup-dotnet@v4nuget pushtodotnet nuget pushwith updated parameter syntax