Combine GitHub and Nuget Release Stage #25318
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
jshigetomi
added
CL-BuildPackaging
TravisEz13
reviewed
Apr 11, 2025
TravisEz13
reviewed
Apr 11, 2025
Collaborator
Author
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
TravisEz13
approved these changes
Apr 11, 2025
Member
|
/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
TravisEz13
approved these changes
Apr 16, 2025
Collaborator
Author
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
TravisEz13
approved these changes
Apr 16, 2025
daxian-dbw
approved these changes
Apr 16, 2025
Contributor
|
📣 Hey @@jshigetomi, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
pwshBot
pushed a commit
to pwshBot/PowerShell
that referenced
this pull request
Apr 16, 2025
9 tasks
pwshBot
pushed a commit
to pwshBot/PowerShell
that referenced
this pull request
Apr 28, 2025
9 tasks
Sysoiev-Yurii
pushed a commit
to Sysoiev-Yurii/PowerShell
that referenced
this pull request
May 12, 2025
Co-authored-by: Justin Chung <[email protected]> Co-authored-by: Travis Plunk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
PR Summary
This pull request includes significant changes to the PowerShell release pipeline configuration, mainly focusing on consolidating the GitHub and NuGet publishing stages and removing redundant stages. The most important changes include renaming and modifying templates, updating parameters, and removing unnecessary stages.
Consolidation of GitHub and NuGet publishing stages:
.pipelines/PowerShell-Release-Official.yml: RenamedSkipPMCPublishtoSkipPublishand updated its description to "Skip Publishing to GitHub and Nuget". Combined thePublishGitHubReleaseandPublishNuGetstages into a singlePublishGitHubReleaseAndNugetstage. [1] [2] [3]Template updates:
.pipelines/templates/release-githubNuget.yml: Renamed fromrelease-githubtasks.ymland added a new jobNuGetPublish. Updated the condition to check theskipPublishparameter and included steps to publish to NuGet. [1] [2] [3]Removal of redundant stages:
.pipelines/PowerShell-Release-Official.yml: Removed thePublishNuGetandReleaseSnapstages, as their functionality is now covered by the consolidatedPublishGitHubReleaseAndNugetstage. [1] [2] [3]Template cleanup:
.pipelines/templates/release-publish-nuget.yml: Removed the entire file as its functionality has been merged intorelease-githubNuget.yml.PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright header