shadowdaoandClaude Sonnet 5 85e2d08f18 ci: fix Windows step shell -- use powershell, not pwsh ...

Real verification push (2b216d3) caught this: explicitly setting
shell: pwsh made the Windows job fail immediately with "Cannot find:
pwsh in PATH". winvm-builder only has the in-box Windows PowerShell 5.1
(powershell.exe), not PowerShell Core -- which is exactly why the original
inline build.yml steps never set `shell:` at all and just relied on the
implicit default. Switched both workflows' Windows steps to
`shell: powershell` explicitly instead of leaving it implicit, so future
edits can't reintroduce this by copying a pwsh example from elsewhere.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RL8abRmgFXkVASHkkqiJbE

2026-09-07 05:15:35 -07:00

..

scripts

ci: add tag-triggered release packaging workflow

2026-09-07 05:06:25 -07:00

workflows

ci: fix Windows step shell -- use powershell, not pwsh

2026-09-07 05:15:35 -07:00