Dashboard › cli › Distillation
afb22827-4d4d-4621-9cfe-6ee3ac3219dc["lore_tm_v1_lxoVsYz6JMMdpdr5FWFGS5gKnJUx7RQ0K-SCmjoKJPk","lore_tm_v1_IrY4TaPqvl7LNLYhrU644voAeSS0IvlfDR_KGnUhdjU","lore_tm_v1_JDgVOIJ94G1FBaC_mAy9Fh8z9vjhhPcX1Pz7suULUpE","lore_tm_v1_cBdAJs0htmFnsa2APmtfrLdpOul-Aeim_qBC5_-p35Y"]
packages/cli/test/commands/cli/upgrade.test.ts verifies pinned stable resolution for 88.88.88: request https://api.github.com/repos/getsentry/toolkit/releases/tags/cli%4088.88.88; after its HTTP 404, request https://api.github.com/repos/getsentry/cli/releases/tags/88.88.88; then request https://api.github.com/repos/getsentry/cli/releases?per_page=30. It must not request Toolkit pagination or any per_page=100 URL.packages/cli/test/commands/cli/upgrade.test.ts test "never uses the cached target after %s" requires both HTTP 403 and a malformed HTTP 200 containing only [{ tag_name: "mcp@1.0.0" }] to produce errors, make exactly 1 request to getsentry/toolkit, and never output "Using cached target".packages/cli/test/commands/cli/upgrade.test.ts test "migrates npm install to standalone binary for a pinned nightly" runs cli upgrade --method npm 0.99.0-dev.1234567890; nightly distribution uses GHCR token → manifest → blob retrieval, with manifest annotation version: "0.99.0-dev.1234567890", layer digest sha256:abc456, a 307 redirect to https://blob.example.com/nightly.gz, and a gzipped binary payload."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"; afterward getReleaseChannel() must be "stable", and the migration process must run exactly once with arguments containing ["--channel", "stable"].packages/cli/test/commands/cli/upgrade.test.ts allows a pinned nightly for a Homebrew installation: cli upgrade --check --method brew 0.99.0-dev.1234567890 validates GHCR manifest tag nightly-0.99.0-dev.1234567890, outputs 0.99.0-dev.1234567890, and does not invoke the migration process.cli upgrade --method brew 1.2.3 to fail before network access with "Homebrew does not support installing a specific version"; it must make zero requests and must not invoke migration, even when the stored release channel is "nightly"."validates an npm stable pin through npm while tracking nightly", with setReleaseChannel("nightly").packages/cli/test/lib/upgrade.test.ts contains a test titled "classifies malformed GitHub release pagination as a network error".fetchLatestFromNpm() tests in packages/cli/test/lib/upgrade.test.ts require an npm registry JSON response { version: "1.2.3" } to return "1.2.3".fetchLatestFromNpm() must throw UpgradeError with "Failed to fetch from npm: 500" for an npm HTTP 500, and throw UpgradeError with "Failed to connect to npm registry: fetch failed" when fetch raises TypeError("fetch failed").fetchLatestFromNpm() must reject an HTTP 200 JSON object without version using "No version found in npm registry".fetchLatestFromNpm() must reject npm latest versions "not-semver", "1.2.3-dev.123", "1.2.3-beta.1", and "1.2.3-rc.1" with "npm registry returned an invalid stable version".UpgradeError("unknown_method") test requires reason === "unknown_method" and the default message "Could not detect installation method. Use --method to specify.".