Distillation

Date: Sep 10, 2026

• 🟡 (02:39) Diff in packages/cli/test/commands/cli.test.ts updates upgrade-command GitHub API mocks from a single release object such as { tag_name: "v0.0.0-dev" } to release-list arrays using namespaced tags such as [{ tag_name: "cli@0.0.0-dev" }].
• 🟡 (02:39) The “specified version does not exist” upgrade test now models source resolution as one latest-release fetch returning [{ tag_name: "cli@99.0.0" }], followed by two exact-tag probes that both return HTTP 404; the test comment was updated to reflect both probes.
• 🟡 (02:39) Additional upgrade tests use Toolkit-style release fixtures including [{ tag_name: "cli@99.99.99" }] and an empty release list [], indicating coverage of release-source fallback or empty-source behavior.
• 🟡 (02:39) packages/cli/test/commands/cli.test.ts adds a resolveUpgradeSource test suite that captures requested URLs, includes table-driven cases, and probes exact release tags via getGitHubReleaseByTagUrl("0.45.0", source).
• 🟡 (02:39) A source fixture added to packages/cli/test/commands/cli.test.ts sets ghcrRepo: "getsentry/cli".
• 🟡 (02:39) Existing upgrade integration coverage shown in the diff includes: curl up-to-date output containing "Method: curl", CLI_VERSION, and "You are already on the target version"; curl --check for version "88.88.88"; immediate rejection of a specific Homebrew version with "Homebrew does not support installing a specific version"; curl upgrade to "0.0.1"; curl --check --method curl stable; brew upgrade with --json; nightly binary download from GHCR using gzipped ELF-like bytes; and getBinaryDownloadUrl("1.0.0") URL construction for the current platform.