fix: upgradePowershell should fall back to pwsh on PowerShell-7-only Windows hosts

Open Beginner friendly
#955 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
bun, powershell, typescript
Domain
cli

Research direction

Read packages/opencode/src/installation/index.ts and inspect upgradePowershell plus the bash installer's Windows AVX2 probe for the existing executable-resolution pattern. Add a focused test for a pwsh-only host, then run the relevant installation tests; done means the upgrade path uses pwsh when available and falls back to powershell.

Written by the indexing model from the issue text.

Description

Found during the v0.8.8 release review (Tech Lead, P2 deferred).

upgradePowershell in packages/opencode/src/installation/index.ts hardcodes the powershell executable (Windows PowerShell 5.1):

return Process.run(["powershell", "-NoProfile", "-ExecutionPolicy", "Bypass", "-Command", `irm ${UPGRADE_INSTALL_PS_URL} | iex`], ...)

On Windows 11 / PowerShell-7-only hosts (or hardened images) where powershell.exe (5.1) is absent, altimate upgrade fails. The bash installer's Windows AVX2 probe already tries powershell.exe then pwsh — the upgrade path should do the same.

Fix: resolve the shell once, preferring pwsh then falling back to powershell (e.g. Bun.which("pwsh") ?? "powershell" or a shared helper), and pass the resolved path to Process.run.

Deferred from v0.8.8 because the self-upgrade path is sensitive and pwsh-only hosts are a subset; tracking for a focused follow-up with a test.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.