Fix package path for release#4258
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the OneBranch NuGet publishing pipeline templates to look for built .nupkg artifacts under Package-Release/ instead of packages/, aligning release publishing steps with an intended artifact directory structure change.
Changes:
- Updated
release-stages.ymlto passpackagePathvalues rooted atPackage-Release/for all released packages. - Updated
publish-nuget-package-job.ymlto default thepackageToPushglob toPackage-Release/{packageName}.*.nupkgwhenpackagePathisn’t provided.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| eng/pipelines/onebranch/stages/release-stages.yml | Updates per-package packagePath values used by the release stage publish jobs. |
| eng/pipelines/onebranch/jobs/publish-nuget-package-job.yml | Changes the default publish glob to target Package-Release/ instead of packages/. |
paulmedynski
approved these changes
May 4, 2026
cheenamalhotra
approved these changes
May 4, 2026
paulmedynski
pushed a commit
that referenced
this pull request
May 7, 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 pipeline configuration to change the expected location of NuGet package artifacts from the
packages/directory toPackage-Release/. This ensures that all package publishing steps reference the correct artifact paths after a directory structure change.Pipeline artifact path updates:
Updated the
packageToPushvariable inpublish-nuget-package-job.ymlto use thePackage-Release/directory instead ofpackages/.Updated all
packagePathparameters inrelease-stages.ymlfor the following packages to use thePackage-Release/directory:Microsoft.SqlServer.ServerMicrosoft.Data.SqlClient.Internal.LoggingMicrosoft.Data.SqlClient.Extensions.AbstractionsMicrosoft.Data.SqlClientMicrosoft.Data.SqlClient.Extensions.AzureMicrosoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider