[release/v7.4.15] Publish .msixbundle package as a VPack#27187
Merged
adityapatwardhan merged 1 commit intoPowerShell:release/v7.4.15from Apr 3, 2026
Conversation
adityapatwardhan
added
the
CL-BuildPackaging
Contributor
There was a problem hiding this comment.
Pull request overview
Backports the upstream change to support publishing the Windows .msixbundle artifact as a OneBranch VPack, including the Store-required PhoneIdentity metadata in the MSIX manifest and a dedicated official pipeline for the VPack flow.
Changes:
- Add
mp:PhoneIdentityto the MSIX manifest template and injectPhoneProductIdduring MSIX packaging. - Update MSIX packaging logic (
New-MSIXPackage) to select the correctPhoneProductIdfor Stable/Preview/LTS packages. - Introduce a new official pipeline to download the produced
.msixbundleartifact and stage it for VPack creation/submission.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
tools/packaging/packaging.psm1 |
Adds PhoneProductId selection and replaces $PHONEPRODUCTID$ into the manifest content during MSIX packaging. |
assets/AppxManifest.xml |
Adds mp:PhoneIdentity placeholder required for Store submission. |
.pipelines/MSIXBundle-vPack-Official.yml |
New pipeline to consume the MSIX bundle artifact and prepare it for VPack publishing. |
| - template: .pipelines/templates/SetVersionVariables.yml@self | ||
| parameters: | ||
| ReleaseTagVar: $(ReleaseTagVar) | ||
| UseJson: no |
There was a problem hiding this comment.
The call to .pipelines/templates/SetVersionVariables.yml@self passes UseJson, but the template defines the parameter as CreateJson. Azure Pipelines template expansion will fail with an unexpected-parameter error. Rename UseJson to CreateJson (e.g., CreateJson: 'no') to match the template signature.
Suggested change
| UseJson: no | |
| CreateJson: no |
daxian-dbw
approved these changes
Apr 3, 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 #25612 to release/v7.4.15
Triggered by @adityapatwardhan 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
Adds the MSIX bundle vPack publishing pipeline and required packaging metadata updates needed for release tooling and store submission flow.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Validated through the original PR's Azure DevOps pipeline runs for msixbundle-vpack, build, and package pipelines. Cherry-pick completed cleanly on release/v7.4.15 after conflict resolution, and resulting branch has a clean working tree.
Risk
REQUIRED: Check exactly one box.
This touches release pipeline and packaging artifacts, so release-process risk is high; scope is constrained to MSIX/vPack publishing and manifest/product-id handling already validated upstream.
Merge Conflicts
Resolved conflicts in .pipelines/PowerShell-Release-Official.yml and .pipelines/templates/SetVersionVariables.yml by preserving release/v7.4.15 pipeline structure and keeping equivalent intended updates for readability/wording.