Update the MSIXBundle-VPack pipeline to create VPack for both LTS and Stable channel packages#27384
Merged
daxian-dbw merged 1 commit intoPowerShell:masterfrom May 5, 2026
Merged
Conversation
… Stable channel packages - Remove signed individual files from the output directory, to avoid the CredSign error that came from nowhere in the pipeline run on 4/23/26 - Update the pipeline to handle creating VPack packages for both the LTS and Stable channels - Move the pack-sign-create-vpack job to a template - Create 2 explicit jobs for creating LTS vpack and stable vpack respectively. The job is guarded by a condition to test if we are supposed to publish to the corresponding channel. The job is skipped if we are not publishing to that channel. - Use different VPack package names for those 2 branches -- `PowerShell7-LTS.Store.app` and `PowerShell7-Stable.Store.app`
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the MSIXBundle-VPack Azure Pipeline to produce VPack artifacts for both LTS and Stable channels, and restructures the bundling/signing logic via a reusable template.
Changes:
- Added a new
create-msixbundle-vpack.ymltemplate that bundles, signs, and stages MSIXBundle output per channel. - Updated the official pipeline to build MSIX packages for the enabled publish channels and run separate LTS/Stable VPack jobs conditionally.
- Removed an LTS-only gating check and added cleanup of the
Signed-$(Runtime)output to avoid signing-related pipeline failures.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| .pipelines/templates/create-msixbundle-vpack.yml | New template job to create/sign/stage an MSIXBundle and prepare VPack inputs per channel. |
| .pipelines/MSIXBundle-vPack-Official.yml | Pipeline now computes enabled publish channels from metadata.json and runs per-channel VPack creation via the new template. |
daxian-dbw
added
the
CL-BuildPackaging
adityapatwardhan
approved these changes
May 5, 2026
| ob_artifactBaseName: 'drop_pack_$(Channel)' | ||
| ob_createvpack_enabled: ${{ parameters.createVPack }} | ||
| ob_createvpack_packagename: 'PowerShell7-$(Channel).Store.app' | ||
| ob_createvpack_owneralias: 'dongbow' |
Member
There was a problem hiding this comment.
does it need to be 1 person, or we can put the maintainers security group. Dont really know what that is used for. If they send emails to this, then having it for a DL might be better.
Member
Author
There was a problem hiding this comment.
I'm not super sure how this will be used. The PowerShell-vPack-Stages.yml one lists Travis as the only owner for now, so I did the same for this one. I will keep an eye on this and change both of them if we decide to use a security group.
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.
PR Summary
Update the
MSIXBundle-VPackpipeline to create VPack for bothLTSandStablechannel packages.create-msixbundle-vpack.yml.PowerShell7-LTS.Store.appandPowerShell7-Stable.Store.appTest pipeline run: https://dev.azure.com/mscodehub/PowerShellCore/_build/results?buildId=675038&view=results
The pipeline skips
Bundle_LTSorBundle_Stablebased ontools/metadata.json.NOTE: It's easier to review the PR when ignoring the whitespace changes with
?w=1: https://github.com/PowerShell/PowerShell/pull/27384/changes?w=1