Dashboard › cli › Distillation
bdf1c96c-d5c6-4bd9-8596-5e43611dc8c2["lore_tm_v1_GyA0z94TyHvsJLv7qf80pImGcGPce6NCwGH5yu_6c9M","lore_tm_v1_3rqeXgMza6oj_qAH_Cmyr1LeTjmj8eu7mvvPgQ1PjGM","lore_tm_v1_F0zkPJfIJ8Q6SilHPTNRsxe-dn9wtqmd7c2HJ9CpEW4","lore_tm_v1_ax7S2TthhuTatCHp8PCm2NZb2z4XSDGtzuPWDyFaavI","lore_tm_v1_uVBfq4sDhuqde77iH_MFyX5VcT8ngd8qFJNcdUV8BJU"]
https://github.com/getsentry/cli/issues/1244), is a sub-task of master merge issue getsentry/cli#1248; one stable bridge CLI release must ship from getsentry/cli before any CLI history is imported into getsentry/sentry-mcp.getsentry/toolkit / ghcr.io/getsentry/toolkit; 2. getsentry/cli / ghcr.io/getsentry/cli.getsentry/cli; every migrated stable CLI release and nightly must therefore be dual-published to Toolkit and legacy CLI endpoints throughout the compatibility window.UPGRADE_SOURCES across src/lib/binary.ts, ghcr.ts, upgrade.ts, and delta-upgrade.ts; mirror ordered fallback in the install script; add a check: script proving the install script and TypeScript resolver use one ordered source list; preserve delta-patch chains (sha256-<binary> / from-version) and cleanup/keep-count parity across both GHCR packages; configure the post-migration Toolkit release flow to dual-publish releases and nightlies to both repositories, keeping getsentry/cli writable until the compatibility window ends.getsentry/cli using the release system’s computed version rather than manually pinning a target; 2. verify a pre-bridge binary upgrades to the bridge release through getsentry/cli; 3. verify the bridge binary handles a 404 from the not-yet-existing getsentry/toolkit source and upgrades through getsentry/cli; 4. verify the install script behaves identically; 5. record the released bridge version in issue #1244, and only then begin 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 between both repositories, which must match; 6. run the same matrix for the install script and one nightly.getsentry/cli may be archived only after telemetry and release evidence show the legacy endpoint is no longer required, and it must remain writable until then.BYK on issue #1244 links the master tracking issue https://github.com/getsentry/cli/issues/1248. (meaning Jul 15, 2026)packages/cli/test/lib/delta-upgrade.test.ts lines 819–854 test fetchRecentReleases(): a successful GitHub API response returns releases ordered 0.14.0, 0.13.0; HTTP 500 and a network TypeError("fetch failed") each return [].packages/cli/test/lib/delta-upgrade.test.ts lines 858–889 test downloadStablePatch(): https://example.com/patch.bin returns Uint8Array([1, 2, 3, 4, 5]), while HTTP 404 and network failure return null.resolveStableChain() tests in packages/cli/test/lib/delta-upgrade.test.ts include: a single hop from 0.13.0 to 0.14.0 with expected digest versionHex("0.14.0"); a parallel two-hop chain 0.13.0 → 0.14.0 → 0.15.0 whose patches remain in oldest-first apply order; null when the target is absent; null when the releases API fails; and null when any patch download fails.0.1.0 to 0.15.0; this exceeds MAX_STABLE_CHAIN_DEPTH of 10, so resolveStableChain() must return null.packages/cli/test/lib/delta-upgrade.test.ts restores globalThis.fetch after each test using originalFetch; setupStableMocks() serves JSON for URLs beginning with https://api.github.com/, serves patch bytes from a Map<string, Uint8Array>, and otherwise returns HTTP 404.packages/cli/package.json specifies Node runtime >=22.15 and package manager pnpm@10.11.0.packages/cli/package.json check scripts are: check:fragments → pnpm tsx script/check-fragments.ts; check:deps → pnpm tsx script/check-no-deps.ts; check:errors → pnpm tsx script/check-error-patterns.ts; check:patches → pnpm tsx script/check-patches.ts; check:docs-sections → pnpm tsx script/generate-docs-sections.ts --check; check:env-coverage → pnpm tsx script/check-env-coverage.ts; and check:stale-refs → pnpm tsx script/check-stale-references.ts. No ordered upgrade-source parity check is currently listed..github/workflows/ci.yml currently invokes pnpm run check:fragments at line 188 and pnpm run check:deps, pnpm run check:errors, pnpm run check:patches, and pnpm run check:stale-refs at lines 244–247; the workflow search showed no ordered upgrade-source parity check.