{{ message }}
[release/v7.4] Use GitHubReleaseTask - #25401
Merged
Travis Plunk (TravisEz13) merged 3 commits intoApr 21, 2025
Merged
Conversation
Travis Plunk (TravisEz13)
changed the title
Travis Plunk (TravisEz13)
added
the
CL-BuildPackaging
Travis Plunk (TravisEz13)
enabled auto-merge (squash)
April 21, 2025 22:10
Member
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Justin Chung (jshigetomi)
approved these changes
Apr 21, 2025
Contributor
Justin Chung (jshigetomi)
added a commit
that referenced
this pull request
Apr 28, 2025
This was referenced Jul 15, 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
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.
Backport of #25398 to release/v7.4
Triggered by Travis Plunk (@TravisEz13) on behalf of Justin Chung (@jshigetomi)
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
Choose either tooling or Customer impact.
Tooling Impact
Customer Impact
[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
[How was the fix verified? How was the issue missed previously? What tests were added?]
Risk
[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]