Skip to content

fix: 🐛 run build scripts under powershell 7.4+ - #484

Merged
jagger merged 1 commit into
devfrom
jagger/fix-build-invokebuild-pwsh
Oct 28, 2026
Merged

jagger merged 1 commit into
devfrom
jagger/fix-build-invokebuild-pwsh

Conversation

@jagger

@jagger jagger commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

The pinned InvokeBuild 5.7.3 and 5.8.4 fail on PowerShell 7.4 and later before any task runs:
A parameter with the name 'ProgressAction' was defined multiple times for the command.
build.ps1, build.library.ps1 and build-release-only.ps1 now pin InvokeBuild 5.12.2.
The fallback Install-Module for InvokeBuild and platyPS uses -Scope CurrentUser, so a non-elevated session can bootstrap them.

On PowerShell 7.6.9, all three scripts complete -Configuration Debug when run directly.
On the same bootstrap probe, InvokeBuild 5.7.3 through 5.8.6 fail and 5.10.4 and 5.12.2 succeed.
CI is unaffected: testimport.yml installs the latest InvokeBuild and calls Invoke-Build directly, which skips the pin.

🤖 Generated with Claude Code

The pinned InvokeBuild 5.7.3/5.8.4 fail before any task runs on
PowerShell 7.4 and later with "A parameter with the name
'ProgressAction' was defined multiple times for the command". Pin
5.12.2 in build.ps1, build.library.ps1 and build-release-only.ps1.

The fallback Install-Module for InvokeBuild and platyPS now uses
-Scope CurrentUser, so a non-elevated session can bootstrap them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jagger
jagger merged commit 8af6a42 into dev Oct 28, 2026
4 checks passed
@jagger
jagger deleted the jagger/fix-build-invokebuild-pwsh branch October 28, 2026 14:21
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