[release/v7.4] Fix the container image for vPack, MSIX vPack and Package pipelines#27016
Merged
adityapatwardhan merged 1 commit intoPowerShell:release/v7.4from Mar 12, 2026
Conversation
adityapatwardhan
added
the
CL-BuildPackaging
TravisEz13
approved these changes
Mar 12, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Backport to release/v7.4 updating OneBranch pipeline configuration to run vPack and coordinated packaging workflows on Windows Server 2022 container images / host version for compatibility and supportability.
Changes:
- Update vPack pipeline
WindowsContainerImagefromltsc2019toltsc2022. - Update coordinated packages pipeline
WindowsContainerImagefromltsc2019toltsc2022. - Explicitly set
WindowsHostVersion.Version: 2022for the coordinated packages pipeline.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.pipelines/PowerShell-vPack-Official.yml |
Switches the Windows container image to ltsc2022 for the vPack pipeline. |
.pipelines/PowerShell-Coordinated_Packages-Official.yml |
Switches the Windows container image to ltsc2022 and pins Windows host version to 2022 for coordinated packaging. |
You can also share your feedback on Copilot code review. Take the survey.
jshigetomi
pushed a commit
to jshigetomi/PowerShell
that referenced
this pull request
Mar 12, 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 #27015 to release/v7.4
Triggered by @adityapatwardhan on behalf of @adityapatwardhan
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 build/packaging pipeline container images from Windows Server 2019 (ltsc2019) to Windows Server 2022 (ltsc2022) and sets the Windows host version to 2022.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Pipeline configuration change only. Verified by reviewing the diff — container images updated from ltsc2019 to ltsc2022 and WindowsHostVersion set to 2022. No functional code changes.
Risk
REQUIRED: Check exactly one box.
This is a pipeline configuration change updating container images and host versions. No functional code is modified. The same changes are already merged and validated on master.
Merge Conflicts
MSIXBundle-vPack-Official.yml was deleted by us (does not exist on release/v7.4). Resolved by accepting the deletion and skipping that file.