From a14e5b5040ccdd83650da6b7d4c8fccf26c285d5 Mon Sep 17 00:00:00 2001 From: Raimund Andree Date: Sun, 11 Oct 2026 13:30:57 +0000 Subject: [PATCH] docs(lab): warn that powershell.exe started from PowerShell 7 inherits its module path A cell of the matrix did nothing when the maintainer started Run-MatrixSequence.ps1 with Start-Process powershell.exe from a PowerShell 7 session: Windows PowerShell 5.1 inherits the PSModulePath of PowerShell 7, cannot load Microsoft.PowerShell.Utility from it, the script stops at its first call of Get-FileHash, and a hidden window leaves no log. The README of the lab kit now says to start the scripts in a Windows PowerShell window, or from PowerShell 7 to set the module path to the three WindowsPowerShell folders first. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant --- Tests/Lab/README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Tests/Lab/README.md b/Tests/Lab/README.md index 2742feb..9fc2a1d 100644 --- a/Tests/Lab/README.md +++ b/Tests/Lab/README.md @@ -176,7 +176,12 @@ A run with `-ModulePath` validates a build. The acceptance of a release is the run with `-Version` of the exact prerelease on the PowerShell Gallery, as `Docs\Contributing\05-Releasing.md` describes. The scripts in the folder [Acceptance](Acceptance) support it, and each runs in Windows PowerShell 5.1 on -the host: +the host. Start them in a Windows PowerShell window. A `powershell.exe` that +PowerShell 7 starts inherits the `PSModulePath` of PowerShell 7, and the script +stops at its first call of `Get-FileHash`, without a log when its window is +hidden; from PowerShell 7, set `$env:PSModulePath` to the three +`WindowsPowerShell\Modules` folders (Documents, Program Files, and System32) +before you start one: - `Test-PublishedRelease.ps1 -Version -OutputPath ` checks a published version and changes nothing: the tag and its commit on `master`,