0.0.10 upgrade: brew install mis-detected as cargo

[Blankeos]

Summary

On 0.0.10 (and earlier upgrade logic), crabcode upgrade could mis-detect a Homebrew install as a Cargo install.

Symptoms

• Crabcode installed via Homebrew (which crabcode → /opt/homebrew/bin/crabcode)
• Running crabcode upgrade required cargo / tried to install to ~/.cargo/bin
• The active Homebrew binary was not upgraded; a stray binary could appear under ~/.cargo/bin/crabcode

Cause

Install-method detection fell through to the cargo heuristic instead of recognizing /opt/homebrew/ (or Cellar) paths.

Status

Fixed in 0.0.11 (“Better upgrade”) — path detection now treats Homebrew Cellar / /opt/homebrew/ as InstallMethod::Homebrew and runs brew upgrade.

Workaround (if still on ≤0.0.10)

brew upgrade blankeos/tap/crabcode
rm -f ~/.cargo/bin/crabcode   # remove stray cargo copy if present

Refs

• src/upgrade.rs — detect_install_method_from_path
• CHANGELOG: 0.0.11 — Better upgrade

[Blankeos]

Issue is solved already, but keeping this issue open for anyone stumbling it on 0.0.10. Will close on 0.0.12