[release/v7.4.16] Update the MSIXBundle-VPack pipeline to create VPack for both LTS and Stable channel packages#27470
Merged
daxian-dbw merged 1 commit intoMay 18, 2026
Conversation
…nd Stable channel packages (PowerShell#27384)
SeeminglyScience
approved these changes
May 18, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Backport of #27384 to release/v7.4.16. Refactors the MSIXBundle vPack pipeline so it produces vPack packages for both LTS and Stable channels (instead of LTS only), driven by tools/metadata.json. The shared bundling/signing/vPack logic is extracted into a reusable template that is instantiated once per channel.
Changes:
- Remove the LTS-only minor-version guard and build both LTS and Stable MSIX packages from a single
Build_MSIX_Packagestep, emitting anEnabledChannelsoutput variable. - Replace the monolithic
Bundlejob with two parameterized template instantiations (LTS,Stable) gated byEnabledChannels. - Add
create-msixbundle-vpack.ymlcontaining the per-channel MSIX filtering, makeappx bundling, signing, staging, and vPack metadata.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .pipelines/MSIXBundle-vPack-Official.yml | Drops LTS-only check, builds both channels, exports EnabledChannels, replaces inline Bundle job with two template references. |
| .pipelines/templates/create-msixbundle-vpack.yml | New per-channel template that downloads MSIX artifacts, filters by channel, builds & signs the bundle, and stages it for vPack creation. |
17da8c9
into
PowerShell:release/v7.4.16
35 of 36 checks passed
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 #27384 to release/v7.4.16
Triggered by @daxian-dbw on behalf of @daxian-dbw
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
Updates the MSIXBundle-VPack pipeline to support creating VPack for both LTS and Stable channel packages in the release branch. Required for correct packaging of this release.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Pipeline change verified via test run in the original PR. The pipeline conditionally skips LTS or Stable bundle based on
tools/metadata.json. No code behavior changes — tooling only.Risk
REQUIRED: Check exactly one box.
Pure CI/CD pipeline change with no runtime code changes. Logic is guarded by conditions based on metadata, so the incorrect channel is automatically skipped.