Distillation

Date: Sep 10, 2026

• 🟡 (12:10) packages/cli/test/lib/upgrade.test.ts expanded upgrade coverage and now imports UPGRADE_SOURCES from ../../src/lib/binary.js and resolveExistingUpgradeVersion from ../../src/lib/upgrade.js.
• 🟡 (12:10) New fetchLatestFromGitHub() pagination coverage tracks request counts, includes product-mismatched release tags such as mcp@9.0.${index}, expects a 2-request pagination flow, and exercises a GitHub Link header pointing to https://api.github.com/repositories/1114546946/releases?per_page=100&page=2.
• 🟡 (12:10) New GitHub release validation coverage checks exact failures including "GitHub returned an invalid release pagination URL", "GitHub returned invalid release metadata", and "No version found in GitHub release"; additional paths include HTTP 404 and network TypeError("fetch failed").
• 🟡 (12:10) New standalone stable-version validation uses test.each(...) to reject invalid versions before network access, including "1.2.3-beta.1".
• 🟡 (12:10) New resolveExistingUpgradeVersion() coverage includes package-manager inputs such as "bun" and an error path for resolveExistingUpgradeVersion("1.0.0").
• 🟡 (12:10) versionExists("curl", "1.0.0") network-failure coverage expects UpgradeError containing "Failed to connect to GitHub"; another mocked path throws Error("HTTP 404"), while HTTP 500 is also exercised.
• 🟡 (12:10) New cancellation coverage verifies rejection with the exact supplied abort reason.
• 🟡 (12:10) New GHCR upgrade-source coverage exercises authentication scope repository:getsentry/toolkit:pull, returns token "toolkit-token", handles manifest metadata including layers: [], and retains a test that returns a version from a GHCR manifest annotation.