Dashboard › cli › Distillation
0482695f-80b8-4e6f-a808-1866dc3c687d["lore_tm_v1_s0n3EqH2xv1jIFBNFw0daqae9QENFTIQ5ofmbPE0J1k"]
"Nightly builds are only available as standalone binaries.", "Migrating to standalone installation...", "Upgraded to", "npm-installed sentry may still appear earlier in PATH", and "npm uninstall -g sentry".releases/latest response such as { tag_name: "v99.99.99" } to the toolkit releases endpoint containing getsentry/toolkit/releases?per_page=100, with release tags such as cli@99.99.99."https://api.github.com/repos/getsentry/toolkit/releases?per_page=30".["cli", "upgrade", "--method", "curl", "0.0.1"] and expecting output containing "Version 0.0.1 not found".v-prefix stripping test changing its mocked GitHub version from CLI_VERSION to "1.0.0".CLI_VERSION to "0.0.0-dev.1".["cli", "upgrade", "--check", "--method", "curl", "nightly"]."Downloading 1.0.0" and "1.0.0" in output instead of interpolating CLI_VERSION; it must not show "Already up to date" and must show "Upgraded to".parseInstallationMethod() tests requiring "pip", "apt", and "" to throw respectively "Invalid method: pip", "Invalid method: apt", and "Invalid method: ".fetchLatestFromGitHub() resolving to "1.2.3" when the GitHub API supplies a matching release.fetchLatestFromGitHub() failure behavior changing from "Failed to fetch from GitHub: 404" to "No CLI upgrade source was found: every source returned HTTP 404".[{ tag_name: "cli@v3.0.0" }], rather than a single { tag_name: "v3.0.0" } latest-release object.reason: "network_error" and ensuring explicit-source HTTP errors are not incorrectly classified as a missing requested version.versionExists("curl", "1.0.0") expected to return true, while versionExists("brew", "99.99.99") is expected to return false.