-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Fix MSIX artifact upload, vPack template, changelog hashes, git tag command #25437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
TravisEz13
approved these changes
Apr 25, 2025
/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
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 28, 2025
Merged
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Backport-7.4.x-Migrated
BackPort-7.5.x-Consider
CL-BuildPackaging
Indicates that a PR should be marked as a build or packaging change in the Change Log
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 introduces several updates to pipeline configurations and templates to improve functionality, maintainability, and clarity. The changes include removing unused stages, refining file paths, enhancing release notes generation, and improving PowerShell script robustness. Below are the most important changes grouped by theme:
Pipeline Configuration Updates:
ReleaseDocker
stage from.pipelines/PowerShell-Release-Official.yml
to streamline the pipeline and eliminate unused functionality.SetVersionVariables.yml
template in.pipelines/PowerShell-vPack-Official.yml
to use a consistent relative path (.pipelines/templates/SetVersionVariables.yml@self
).Release Notes Enhancements:
.pipelines/templates/release-githubNuget.yml
by appending SHA256 hashes of release artifacts to the changelog using aStringBuilder
. This ensures better traceability of release files.PowerShell Script Improvements:
Copy-Item
operation in.pipelines/templates/release-create-msix.yml
by adding a check to ensure the destination directory exists before copying files.PowerShell@2
tasks in.pipelines/templates/release-githubNuget.yml
for better readability and alignment with modern Azure DevOps practices. [1] [2]Miscellaneous Updates:
.pipelines/templates/release-githubNuget.yml
to clearly label the release with the version tag (e.g., "v1.0.0 Release of PowerShell").PR Context
PR Checklist
.h
,.cpp
,.cs
,.ps1
and.psm1
files have the correct copyright header