Dashboard › cli › Distillation
6f6b4c3c-2091-4d21-aeff-584a7e12d48b["lore_tm_v1_qzQjdq22MV3O1CIt91G-zXqDL-PNKPdHRIb31Sd8vzI","lore_tm_v1_iUuRhrR5BDca_a9tQmgmhPnNoFudDbZF5O6hm2NkMcA","lore_tm_v1_Bat0wxRjpkoRZvr5WykZK3LAuoUH5dnHDBnRZdxo62Y","lore_tm_v1_HKKi1YC7Fe-dlK7t9Fuf1ZMAGapLnnBlu62tsOwzF50"]
packages/cli/test/lib/binary.test.ts changes update getBinaryDownloadUrl("1.0.0") expectations from /1.0.0/ under https://github.com/getsentry/cli/releases/download/ to /cli@1.0.0/ under https://github.com/getsentry/toolkit/releases/download/.getGitHubReleaseByTagUrl, resolveUpgradeSource, UPGRADE_SOURCES, and UpgradeSourceNotFoundError: the first source is used when available, fallback to the legacy source occurs only on HTTP 404, and resolution fails after every source returns 404.0.14.0 and 0.13.0 to cli@0.14.0 and cli@0.13.0; GitHub release-list requests now target api.github.com/repos/getsentry/toolkit/releases by default.resolveStableChain("0.13.0", "0.14.0", undefined, LEGACY_UPGRADE_SOURCE) to query only https://api.github.com/repos/getsentry/cli/releases?per_page=12 and never access getsentry/toolkit.packages/cli/test/lib/release-notes.test.ts changes add tests for fetchChangelog and fetchRecentReleases using explicit sources from UPGRADE_SOURCES; stable release notes must remain on an explicitly selected legacy source, while Toolkit-selected flows must not access the legacy repository.getVersionCheckInfo().lastChecked is null, shouldCheckForUpdate is true, and maybeCheckForUpdateInBackground() should initiate a check without throwing.7d62ffa8317f9b98be0dc4afec0a927c1cabb0b7 — fix(cli): preserve paginated request cancellation; 2. 878459c490576dbb7abb76d3a3dc1b5d9fc62c1f — fix(cli): fail closed on upgrade metadata; 3. e22f0eba66298a7228a988a4adcf1ec5be85227b — fix(cli): preserve source and cancellation provenance; 4. dcf6719995800d28d6f88a8c709abe4aa3d0b6db — test(cli): validate GitHub request origin; 5. f1c10a6cb1a753b8c4b8c613cd78735c3f12cba6 — fix(cli): preserve pinned upgrade contracts; 6. e565b1afb39a341605adc883de8812851de7d581 — fix(cli): validate stable upgrade metadata; 7. 4a1d5bad105c006193c68459175f5eb3c7f78e08 — test(cli): update pinned version fixture; 8. 2f9b5d0d26124d445a916b8bfc584ad518720584 — fix(cli): isolate pinned upgrade resolution; 9. c6030fbf4d0c190f037c86d832edb6680d3e54ab — fix(cli): bind nightly manifests to versions; 10. b6484e0fb1eb0f8bce68272d538f5c3b26cd5bd5 — fix(cli): validate resolved upgrade metadata; 11. c8c815bbecf472061ec02ab96d1a31f23f078d01 — fix(cli): validate GitHub release pagination; 12. 5ffa5cd0fe02c0a5dc5bec9a8a099f4135c0b447 — fix(cli): harden upgrade source resolution; 13. dbee7e9f2a4555e044f74dfebad002cccfa43a1f — test(cli): update toolkit upgrade fixtures; 14. 723375b6ce4e37884e760fa0f848e7e7e3effcc9 — fix(cli): address upgrade review findings; 15. 9c874298e3b57515ba36d35140627a668a46dc7b — fix(cli): address toolkit bridge review; 16. 04867eaf9b412a62d4b1ea1c59c2b382c557bd0b — feat(cli): add toolkit upgrade bridge.7d62ffa8317f9b98be0dc4afec0a927c1cabb0b7, authored and committed by Burak Yigit Kaya <byk@sentry.io>, changes packages/cli/src/lib/binary.ts and packages/cli/test/lib/upgrade.test.ts with 24 insertions across 2 files. (meaning Sep 10, 2026)fetchWithUpgradeError (packages/cli/src/lib/binary.ts) checks init.signal?.aborted after customFetch(url, init) throws and rethrows init.signal.reason, preserving arbitrary cancellation reasons instead of wrapping them as upgrade errors; existing AbortError rethrow behavior remains."preserves an arbitrary abort reason during pagination" in packages/cli/test/lib/upgrade.test.ts creates an AbortController, uses reason { kind: "cancelled" }, returns a first page containing { tag_name: "mcp@9.0.0" } with a Link header to https://api.github.com/repositories/1114546946/releases?per_page=100&page=2, aborts and throws the reason on page 2, then verifies fetchLatestFromGitHub(controller.signal) rejects with that exact object and exactly 2 requests occurred.