[release/v7.5.6] Redo windows image fix to use latest image#27222
Merged
daxian-dbw merged 1 commit intoApr 9, 2026
PowerShell:release/v7.5.6PowerShell/PowerShell:release/v7.5.6from
daxian-dbw:backport/release/v7.5.6/27198-22f62e859daxian-dbw/PowerShell:backport/release/v7.5.6/27198-22f62e859Copy head branch name to clipboard
Merged
[release/v7.5.6] Redo windows image fix to use latest image#27222daxian-dbw merged 1 commit intoPowerShell:release/v7.5.6PowerShell/PowerShell:release/v7.5.6from daxian-dbw:backport/release/v7.5.6/27198-22f62e859daxian-dbw/PowerShell:backport/release/v7.5.6/27198-22f62e859Copy head branch name to clipboard
daxian-dbw merged 1 commit into
PowerShell:release/v7.5.6PowerShell/PowerShell:release/v7.5.6from
daxian-dbw:backport/release/v7.5.6/27198-22f62e859daxian-dbw/PowerShell:backport/release/v7.5.6/27198-22f62e859Copy head branch name to clipboard
Conversation
Co-authored-by: Justin Chung <chungjustin@microsoft.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Backports the main-branch change to update release packaging pipeline variable templates so Windows jobs run on the supported LTSC 2022 OneBranch container image (instead of LTSC 2019), keeping the release/v7.5.6 packaging environment aligned with current tooling.
Changes:
- Update
WindowsContainerImagein vPack variable template toonebranch.azurecr.io/windows/ltsc2022/vse2022:latest. - Update
WindowsContainerImagein Coordinated Packages variable template toonebranch.azurecr.io/windows/ltsc2022/vse2022:latest.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .pipelines/templates/variables/PowerShell-vPack-Variables.yml | Switches the Windows container image for vPack repackaging jobs to LTSC 2022. |
| .pipelines/templates/variables/PowerShell-Coordinated_Packages-Variables.yml | Switches the Windows container image for coordinated packaging jobs to LTSC 2022. |
SeeminglyScience
approved these changes
Apr 9, 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 #27198 to release/v7.5.6
Triggered by @daxian-dbw on behalf of @jshigetomi
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 pipeline variable templates to use the current supported Windows LTSC 2022 container image for release packaging. This is required to keep release branch packaging infrastructure aligned with the supported build environment.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Cherry-pick applied cleanly to release/v7.5.6. The backport changes only two pipeline variable templates and relies on release branch CI to validate the packaging environment after PR creation.
Risk
REQUIRED: Check exactly one box.
Medium risk because the change affects release packaging infrastructure and the Windows build environment, but the scope is limited to two variable values and matches the validated change on main.