Distillation

🔴 (02:37) User specified sentry cli upgrade nightly as the command to “Switch to nightly channel and update.”
🔴 (02:37) User stated installation-method detection must always check for Homebrew first because stored install information may be stale.
🔴 (02:37) User stated nightly builds are distributed only as standalone binaries through GitHub releases.
🔴 (02:37) User stated latest-nightly resolution uses the rolling "nightly" release tag, while a specific nightly version uses that version’s release tag.
🔴 (02:37) User stated that when switching to nightly and the current installation method is not curl, the upgrade must use the standalone-binary path because nightly is GitHub-only.
🔴 (02:37) User’s upgrade help text distinguishes sentry cli upgrade nightly for switching to nightly and updating from sentry cli upgrade 0.5.0 for installing a specific stable version.
🔴 (02:37) User stated known curl installation directories honor an absolute XDG_BIN_HOME, matching determineInstallDir precedence.
🔴 (02:37) User stated Windows package-manager executables for npm, pnpm, and yarn are .cmd batch files.
🔴 (02:37) User’s legacy installation-method detection order is curl paths, then subprocess calls, then the node_modules path, after the mandatory Homebrew-first check.
🔴 (02:37) User stated detected installation methods are automatically persisted for future runs on a best-effort basis.
🔴 (02:37) User stated standalone-version existence checks return false only for HTTP 404 (tag not found); other HTTP and network failures are not treated as a missing version.
🔴 (02:37) User’s binary-download implementation writes each chunk fully by looping over short writes and releases the output file descriptor synchronously before returning so the caller can immediately spawn the downloaded binary.

Distillation

Observations