Distillation

Date: September 10, 2026

• 🔴 (03:06) In packages/cli/test/commands/cli.test.ts, upgrade-command GitHub mocks were updated from the legacy releases/latest response { tag_name: "v0.0.0-dev" } to the Toolkit releases-list endpoint matching getsentry/toolkit/releases?per_page=100, returning [{ tag_name: "cli@0.0.0-dev" }].
• 🔴 (03:06) Version mocks in packages/cli/test/commands/cli.test.ts now represent Toolkit release tags as cli@${version}; a fallback mock still returns a legacy single-release object such as { tag_name: "88.88.88" }.
• 🔴 (03:06) The nightly --check test in packages/cli/test/commands/cli.test.ts was changed from asserting “already on target” with CLI_VERSION to asserting that the valid nightly target 0.0.0-dev.1 is shown.
• 🔴 (03:06) Upgrade-source ordering tests assert that Toolkit is checked before the legacy CLI repository getsentry/cli.
• 🔴 (03:06) resolveUpgradeSource() tests cover: selecting the first source when its probe succeeds; trying the next source when the first probe returns HTTP 404 and the second returns HTTP 200; and yielding an error matching { name: "UpgradeSourceNotFoundError" } when no source resolves.
• 🔴 (03:06) Upgrade-source probe tests construct source-specific URLs with getGitHubReleaseByTagUrl("0.45.0", source).
• 🔴 (03:06) Curl full-upgrade tests continue to verify that child_process.spawn invokes the downloaded entry binary with setup, includes --ensure-auth-scopes, and surfaces Setup failed with exit code 1 when setup exits unsuccessfully.