[release/v7.4.21] Change Windows CI to stop using PowerShell 5.1 - #28049
Merged
Aditya Patwardhan (adityapatwardhan) merged 1 commit intoSep 22, 2026
Conversation
Aditya Patwardhan (adityapatwardhan)
requested a review
from a team
as a code owner
September 21, 2026 21:22
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Copilot started reviewing on behalf of
Aditya Patwardhan (adityapatwardhan)
September 21, 2026 21:22
View session
Contributor
There was a problem hiding this comment.
Copilot review overview
🔵 Needs a closer look
The change alters the PowerShell host used by Windows CI and requires final human validation.
Review effort: Lite
Findings: None
What changed in this PR
Updates Windows CI to use PowerShell Core instead of Windows PowerShell 5.1.
Changes:
- Changes the Windows bootstrap shell to
pwsh. - Removes obsolete PowerShell 5.1 documentation.
| File | Description |
|---|---|
tools/WindowsCI.psm1 |
Removes obsolete host requirement documentation. |
.github/actions/test/windows/action.yml |
Runs Windows bootstrap using PowerShell Core. |
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Aditya Patwardhan (adityapatwardhan)
enabled auto-merge (squash)
September 22, 2026 19:19
Patrick Meinecke (SeeminglyScience)
approved these changes
Sep 22, 2026
Aditya Patwardhan (adityapatwardhan)
merged commit Sep 22, 2026
b6fd898
into
PowerShell:release/v7.4.21
39 checks passed
Aditya Patwardhan (adityapatwardhan)
deleted the
backport/release/v7.4.21/27940-13b2fd125
branch
September 22, 2026 20:20
Justin Chung (jshigetomi)
approved these changes
Sep 23, 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 #27940 to release/v7.4.21
Triggered by Aditya Patwardhan (@adityapatwardhan) on behalf of Dongbo Wang (@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
Stops Windows CI from depending on Windows PowerShell 5.1 and uses the supported PowerShell Core execution path for release-branch validation.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Cherry-pick completed cleanly, git diff --check passed, and tools/WindowsCI.psm1 parses successfully with no conflict markers. Windows workflow execution will be validated by backport CI.
Risk
REQUIRED: Check exactly one box.
High risk because this changes the PowerShell host used by Windows CI. The implementation is narrowly scoped to the workflow action and WindowsCI module adjustment already validated on master.