Update Netherite publish.yml NuGet release step#476
Merged
Conversation
nytian
approved these changes
May 20, 2026
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.
This pull request updates the NuGet publishing process in the CI pipeline to publish multiple packages separately, improves maintainability, and switches to a newer, more robust publishing task. The previous single-job approach is replaced with three distinct jobs, each targeting a specific package, and the legacy
DotNetCoreCLI@2task is replaced with the1ES.PublishNuget@1task for better integration and validation.NuGet publishing pipeline improvements:
nugetReleasejob with three dedicated jobs for publishingMicrosoft.Azure.DurableTask.Netherite,Microsoft.Azure.DurableTask.Netherite.AzureFunctions, andMicrosoft.Azure.Functions.Worker.Extensions.DurableTask.NetheriteNuGet packages, allowing for more granular control and easier troubleshooting.DotNetCoreCLI@2task to the1ES.PublishNuget@1task for pushing packages to NuGet, which provides better support for skipping duplicates and improved SDL tooling integration.