Dashboard › cli › Distillation
01ba6ffe-1f4e-41a5-a2d8-cfbd1d4bf5af["lore_tm_v1_m7A7H4KH9fuSLxWwl_NtuFZVDCkyx1Yegwnp8lDftfU"]
nightly release channel and using the npm installation method triggers migration.packages/cli/test/commands/cli.test.ts upgrade-command mocks to return GitHub release-list data such as [{ tag_name: "cli@1.0.0" }] instead of a single release object { tag_name: "v0.0.0-dev" }.--check mode test from asserting “already on the target version” when current equals latest to asserting display of the current and latest stable versions, with mocked stable version "1.0.0".getsentry/cli/releases?per_page=30.["cli", "upgrade", "--check", "--method", "curl", "nightly"] and expect output containing Channel: nightly, nightly version 0.99.0-dev.9999999999, and Run 'sentry cli upgrade' to update.Checking for updates, Downloading 99.99.99, Upgraded to, and 99.99.99.--force upgrade test to verify that --force downloads the resolved target, using version "1.0.0", rather than framing it only as bypassing an “already up to date” check for CLI_VERSION."", ".download", ".old", and ".lock" under the migration binary path, then calls clearInstallInfo().setReleaseChannel("nightly") setup while retaining migration behavior coverage.getGitHubReleaseByTagUrl, resolveUpgradeSource, UPGRADE_SOURCES, and UpgradeSourceNotFoundError from packages/cli/src/lib/binary.js, including a new describe("resolveUpgradeSource", ...) suite.