Skip to content

Claim PowerShell 7.4+ support instead of 7.2+#381

Merged
nohwnd merged 1 commit into
mainfrom
claim-powershell-7-4-support
Jun 29, 2026
Merged

Claim PowerShell 7.4+ support instead of 7.2+#381
nohwnd merged 1 commit into
mainfrom
claim-powershell-7-4-support

Conversation

@nohwnd

@nohwnd nohwnd commented Jun 29, 2026

Copy link
Copy Markdown
Member

Summary

Pester 6 ships a net8.0 assembly for PowerShell 7 (plus net462 for Windows PowerShell 5.1). A net8.0 assembly cannot load on the .NET 6 / .NET 7 runtimes used by PowerShell 7.2 / 7.3, so claiming support for those versions is inaccurate. They are also both out of support from Microsoft per the PowerShell support lifecycle — the oldest supported release is 7.4 (LTS, .NET 8).

Changes

  • docs/introduction/installation.mdx — "PowerShell 7.2 and above" → "PowerShell 7.4 and above".
  • docs/migrations/v5-to-v6.mdx — "PowerShell 7.2+" support claims (heading + body) → "PowerShell 7.4+".

Companion to pester/Pester#2811, which fixes the same claim in the README and the 6.0.0 release notes.

Pester 6 ships a net8.0 assembly for PowerShell 7, which cannot load on
the .NET 6/.NET 7 runtimes of PowerShell 7.2/7.3. Those versions are also
out of support from Microsoft, so the oldest supported PowerShell is 7.4
(LTS, .NET 8). Update the installation and v5-to-v6 migration docs to claim
7.4+ instead of 7.2+.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@nohwnd nohwnd merged commit 522ed68 into main Jun 29, 2026
4 checks passed
@nohwnd nohwnd deleted the claim-powershell-7-4-support branch June 29, 2026 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant