Skip to content

[release/v7.4.21] Change Windows CI to stop using PowerShell 5.1 - #28049

Merged
Aditya Patwardhan (adityapatwardhan) merged 1 commit into
PowerShell:release/v7.4.21from
adityapatwardhan:backport/release/v7.4.21/27940-13b2fd125
Sep 22, 2026
Merged

Aditya Patwardhan (adityapatwardhan) merged 1 commit into
PowerShell:release/v7.4.21from
adityapatwardhan:backport/release/v7.4.21/27940-13b2fd125

Conversation

@adityapatwardhan

Copy link
Copy Markdown
Member

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

  • Required tooling change
  • Optional tooling change (include reasoning)

Stops Windows CI from depending on Windows PowerShell 5.1 and uses the supported PowerShell Core execution path for release-branch validation.

Customer Impact

  • Customer reported
  • Found internally

Regression

REQUIRED: Check exactly one box.

  • Yes
  • No

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
  • Medium
  • Low

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.

@adityapatwardhan Aditya Patwardhan (adityapatwardhan) added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Sep 21, 2026
Copilot AI lite review requested due to automatic review settings September 21, 2026 21:22
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@adityapatwardhan Aditya Patwardhan (adityapatwardhan) changed the title [release/v7.4.21] Change Windows CI to stop using PowerShell 5.1 WIP: [release/v7.4.21] Change Windows CI to stop using PowerShell 5.1 Sep 22, 2026
@adityapatwardhan Aditya Patwardhan (adityapatwardhan) changed the title WIP: [release/v7.4.21] Change Windows CI to stop using PowerShell 5.1 [release/v7.4.21] Change Windows CI to stop using PowerShell 5.1 Sep 22, 2026
@adityapatwardhan
Aditya Patwardhan (adityapatwardhan) merged commit b6fd898 into PowerShell:release/v7.4.21 Sep 22, 2026
39 checks passed
@adityapatwardhan
Aditya Patwardhan (adityapatwardhan) deleted the backport/release/v7.4.21/27940-13b2fd125 branch September 22, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants