[release/v7.6.4] Separate NuGet publish into its own stage after pushing the git tag#27652
Open
SeeminglyScience wants to merge 1 commit into
Conversation
…owerShell#27611) Co-authored-by: Justin Chung <chungjustin@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Backports the release-pipeline restructuring to release/v7.6.4 by separating NuGet publishing into its own stage that runs only after the git tag is pushed and the GitHub draft release is made public, improving release sequencing correctness.
Changes:
- Split the former combined GitHub+NuGet publish stage into
PublishGitHubReleaseandPublishNugetRelease, with explicit stage dependencies to enforce ordering. - Added a dedicated NuGet publishing template (
release-Nuget.yml) and wired it into the new stage. - Removed the NuGet publishing job from the GitHub release template (
release-github.yml) so it only handles GitHub release drafting.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.pipelines/templates/stages/PowerShell-Release-Stages.yml |
Splits GitHub vs NuGet publishing into separate stages and updates stage dependencies/order. |
.pipelines/templates/release-Nuget.yml |
New template encapsulating NuGet package publish job/steps. |
.pipelines/templates/release-github.yml |
Removes NuGet publish job so the template focuses on GitHub release draft creation. |
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.
Backport of #27611 to release/v7.6.4
Triggered by @SeeminglyScience on behalf of @jshigetomi
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Separates NuGet publishing into a dedicated stage that runs after the git tag is pushed and the draft release is made public, ensuring correct ordering in the release pipeline. Required for the 7.6.4 release pipeline to function correctly.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
This is a pipeline restructuring change. Verified by reviewing the YAML diff and confirming stage dependencies are correctly set. The 7.4.x and 7.5.x backports (#27648, #27650) are already open and serve as reference for the expected shape of the change.
Risk
REQUIRED: Check exactly one box.
Pure CI/pipeline change that only affects the release pipeline structure. No runtime code changes. The same change was successfully applied to 7.4.x and 7.5.x branches.