Use GitHubReleaseTask#25398
Merged
Merged
Conversation
Collaborator
Author
|
This task will not push a tag, it will only prefill the draft with a tag name. The tag will push on publishing of the draft. |
TravisEz13
reviewed
Apr 21, 2025
TravisEz13
reviewed
Apr 21, 2025
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
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 21, 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 21, 2025
9 tasks
pwshBot
pushed a commit
to pwshBot/PowerShell
that referenced
this pull request
Apr 21, 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 <chungjustin@microsoft.com> Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
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
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 updates the release pipeline to replace the previous "Set Tag and Upload Tools" stage with a new "Set Tag and Upload Changelog" stage. The changes streamline the release process by removing tool-related steps and introducing changelog management. Below are the most important changes grouped by theme:
Pipeline Stage Updates:
setReleaseTagAndUploadToolstosetReleaseTagAndChangelogin.pipelines/PowerShell-Release-Official.yml. Updated the display name and corresponding template reference torelease-SetTagAndChangelog.yml. [1] [2]Template Modifications:
.pipelines/templates/release-SetTagAndTools.ymlto.pipelines/templates/release-SetTagAndChangelog.yml. Updated the job name and display name accordingly.release-SetTagAndChangelog.ymltemplate, focusing the job solely on changelog-related tasks.GitHub Release Enhancements:
release-githubNuget.ymltemplate to replace the usage ofSetTagAndToolsoutputs withSetTagAndChangelogoutputs for variables likeReleaseTagandVersion. [1] [2]release-notes.md) and set variables for GitHub release tasks, such asIsPreReleaseandReleaseNotesFilePath.GitHubRelease@1task for creating GitHub releases, replacing the previousPublish-ReleaseDraftstep.These changes simplify the pipeline by removing tool-related operations and enhancing changelog and release management.
PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright header