[release/v7.6.1] Redo windows image fix to use latest image#27217
Merged
daxian-dbw merged 1 commit intoApr 9, 2026
PowerShell:release/v7.6.1PowerShell/PowerShell:release/v7.6.1from
daxian-dbw:backport/release/v7.6.1/27198-22f62e859daxian-dbw/PowerShell:backport/release/v7.6.1/27198-22f62e859Copy head branch name to clipboard
Merged
[release/v7.6.1] Redo windows image fix to use latest image#27217daxian-dbw merged 1 commit intoPowerShell:release/v7.6.1PowerShell/PowerShell:release/v7.6.1from daxian-dbw:backport/release/v7.6.1/27198-22f62e859daxian-dbw/PowerShell:backport/release/v7.6.1/27198-22f62e859Copy head branch name to clipboard
daxian-dbw merged 1 commit into
PowerShell:release/v7.6.1PowerShell/PowerShell:release/v7.6.1from
daxian-dbw:backport/release/v7.6.1/27198-22f62e859daxian-dbw/PowerShell:backport/release/v7.6.1/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
Backport of #27198 to release/v7.6.1, updating OneBranch pipeline variable templates so the release branch uses the latest supported Windows LTSC 2022 build container image.
Changes:
- Update
WindowsContainerImagein vPack variable template from LTSC 2019 to LTSC 2022. - Update
WindowsContainerImagein Coordinated Packages variable template from LTSC 2019 to LTSC 2022.
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 Windows container image reference to windows/ltsc2022/vse2022:latest for vPack-related pipelines. |
| .pipelines/templates/variables/PowerShell-Coordinated_Packages-Variables.yml | Switches Windows container image reference to windows/ltsc2022/vse2022:latest for coordinated packages pipelines. |
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.6.1
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
Backports the Windows container image update in release pipeline variable templates so release/v7.6.1 uses the latest supported LTSC 2022 build environment.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Verified by cherry-picking onto release/v7.6.1 without conflicts. No local pipeline run was performed; CI on the backport PR will validate the updated build environment references in the release branch context.
Risk
REQUIRED: Check exactly one box.
Medium risk because the change affects the Windows build environment used by release pipelines. The scope is limited to two variable template updates and the change cherry-picked cleanly, but infrastructure image changes can have broad CI impact.