[release/v7.6.2] Update the MSIXBundle-VPack pipeline to create VPack for both LTS and Stable channel packages#27435
Merged
daxian-dbw merged 1 commit intoMay 13, 2026
Conversation
…nd Stable channel packages (PowerShell#27384)
Contributor
There was a problem hiding this comment.
Pull request overview
Backport of #27384 to release/v7.6.2. Refactors the MSIXBundle-VPack pipeline to support both LTS and Stable channels by extracting the bundle/sign/VPack job into a reusable template invoked once per channel, gated by tools/metadata.json publish flags. Also drops the previous LTS-only minor-version guard and removes signed individual files from the output directory to avoid CredSign errors.
Changes:
- Removes the LTS-only even-minor-version guard and adds metadata-driven LTS/Stable channel detection that emits an
EnabledChannelsoutput variable. - Extracts the MSIXBundle pack/sign/VPack job into
create-msixbundle-vpack.ymland instantiates it twice (LTS, Stable) with channel-specific package names (PowerShell7-LTS.Store.app/PowerShell7-Stable.Store.app) and conditional execution. - Cleans up
Signed-$(Runtime)folder after packaging to avoid signed individual files appearing in output.
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 | Replaces inline Bundle job with two template invocations; adds metadata-based channel selection and EnabledChannels output variable consumed by the next stage. |
| .pipelines/templates/create-msixbundle-vpack.yml | New reusable template that builds, signs, and creates a per-channel VPack of the msixbundle, gated on EnabledChannels. |
SeeminglyScience
approved these changes
May 13, 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
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.6.2
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
Refactors MSIXBundle-VPack pipeline to support both LTS and Stable channel VPack creation. Moves job logic to a reusable template, adds explicit per-channel jobs with conditional guards, and uses distinct VPack package names (PowerShell7-LTS.Store.app / PowerShell7-Stable.Store.app). Also removes signed individual files from output to avoid CredSign errors.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Validated via a test pipeline run (build 675038) showing correct conditional skipping of LTS/Stable jobs based on metadata.json. No code changes requiring unit tests.
Risk
REQUIRED: Check exactly one box.
Pipeline-only change that restructures the MSIXBundle-VPack job into a template and adds separate LTS/Stable jobs. No runtime code changes. Risk is limited to pipeline execution correctness.