Skip to content

fix: Windows installer upgrades existing WSL installs - #2

Merged
marioolf merged 1 commit into
mainfrom
dev
Jul 13, 2026
Merged

marioolf merged 1 commit into
mainfrom
dev

Conversation

@marioolf

Copy link
Copy Markdown
Owner

Installer fixes

Installers are served from main, so these take effect for real users on merge.

Fixed

  • install.ps1 now upgrades an existing install. It used to skip the Linux binary whenever crabby was already present in WSL, so re-running irm ... | iex never updated it — an install would stay stuck on the old version (this is exactly what happened trying to pick up v0.5.0). It now always runs install.sh, which overwrites in place with the latest release.
  • install.sh no longer prints tmp: unbound variable on exit. The cleanup trap referenced a function-local variable that was out of scope by the time it ran under set -u, so the temp dir also leaked. tmp is now script-scoped.

Both verified in WSL: install.sh exits cleanly and upgrades 0.4.3 → 0.5.0 in place.

install.ps1 skipped the Linux binary whenever crabby was already present
in WSL, leaving existing installs stuck on the old version. Always run
install.sh, which overwrites in place with the latest release.

Also fix a 'tmp: unbound variable' error from install.sh's cleanup trap,
which referenced a function-local out of scope under set -u.
@marioolf
marioolf merged commit e2be5bb into main Jul 13, 2026
1 check passed
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