Dashboard › cli › Distillation
e2cae487-1d91-4ee8-9caf-e24493d10ea0["lore_tm_v1_dUjSPvUK31iQ9vBCXJIO-LL8uPu24h4Ch2gCKehuMrg","lore_tm_v1_cco-OttrrlssQrHil-mPtBnPkV8MNqVFTnGiXBjsrMM","lore_tm_v1_zcP2wRR_Hxq3-qZ2A-DdKczlZu_gcLZWLvWhAoca2Z8","lore_tm_v1_ehUq8N9ko2UjT2Y28tcg4qWz-yc0mAqWI6awAtMc_Mw","lore_tm_v1_t9RG5AeQPz71H_BcqH8NuOm2tya3xiA37vRzYcNdqv0"]
getsentry/toolkit / ghcr.io/getsentry/toolkit; 2. getsentry/cli / ghcr.io/getsentry/cli.getsentry/cli; during the compatibility window, every migrated stable CLI release and nightly must therefore be dual-published to Toolkit and the legacy CLI endpoints.UPGRADE_SOURCES across src/lib/binary.ts, ghcr.ts, upgrade.ts, and delta-upgrade.ts; mirroring ordered fallback in the install script; adding a check: script for source-list/order parity; preserving delta-patch chains (sha256-<binary> / from-version) plus cleanup/keep-count parity across both GHCR packages; and configuring Toolkit’s post-migration flow to dual-publish stable releases and nightlies while keeping getsentry/cli writable.getsentry/cli#1248: one stable release must ship from getsentry/cli before any CLI history is imported into getsentry/sentry-mcp.getsentry/cli using the dual-source resolver and the release system’s computed version rather than a manually pinned target.getsentry/cli; 2. the bridge binary handles a 404 from the not-yet-existing getsentry/toolkit source and upgrades through getsentry/cli; 3. the install script behaves identically; 4. the released bridge version is recorded before beginning getsentry/cli#1239.getsentry/cli; 3. verify the bridge binary and a Toolkit-built binary upgrade through getsentry/toolkit; 4. simulate a Toolkit 404 and verify both new binaries fall back to getsentry/cli; 5. compare release assets, SHA-256 values, GHCR manifests, and delta-chain metadata across repositories and require exact matches; 6. repeat the matrix for the install script and one nightly.getsentry/cli may be archived only after telemetry and release evidence show that the legacy endpoint is no longer required, and it must remain writable until then.packages/cli/src/lib/binary.ts defines UPGRADE_SOURCES with getsentry/toolkit first and getsentry/cli second for both githubRepo and ghcrRepo; PRIMARY_UPGRADE_SOURCE is UPGRADE_SOURCES[0].packages/cli/src/lib/upgrade.ts uses UPGRADE_SOURCES as default resolver input while allowing an explicit UpgradeSource to restrict resolution to [source].packages/cli/test/lib/upgrade.test.ts coverage checks stable GitHub resolution against https://api.github.com/repos/getsentry/toolkit/releases?per_page=100, with fallback to https://api.github.com/repos/getsentry/cli/releases/latest.packages/cli/test/lib/upgrade.test.ts coverage verifies that Toolkit’s package-prefixed tag endpoint https://api.github.com/repos/getsentry/toolkit/releases/tags/cli%401.0.0 falls back on HTTP 404 to the legacy unprefixed endpoint https://api.github.com/repos/getsentry/cli/releases/tags/1.0.0.packages/cli/test/lib/upgrade.test.ts coverage verifies that transport-error text such as "Failed to connect to GitHub" is not classified as a missing source and therefore does not trigger 404-style fallback.set +e because “Telemetry must never fail the script.”