Distillation

Date: Sep 10, 2026

• 🔴 (00:24) packages/cli/package.json identifies package sentry version 0.45.0-dev.0, requires Node.js >=20.0, uses development runtime Node.js >=22.15, and pins package manager pnpm@10.11.0.
• 🔴 (00:24) packages/cli/package.json build/test workflow includes build via pnpm tsx script/build.ts --single, build:all via pnpm tsx script/build.ts, test delegating to test:unit, test:unit running Vitest over test/lib test/commands test/types test/script --coverage, test:changed using vitest run --changed, and test:e2e running vitest run test/e2e.
• 🔴 (00:24) packages/cli/package.json generation scripts include generate:parser, generate:sdk, generate:skill, generate:banner, generate:docs, generate:docs-sections, generate:schema, and generate:command-docs; generate:docs runs banner, parser, command-docs, skill, and docs-sections generation in that order.
• 🔴 (00:24) packages/cli/package.json check scripts include check:fragments, check:deps, check:errors, check:patches, check:docs-sections, check:env-coverage, and check:stale-refs.
• 🔴 (00:25) Branch feat/toolkit-bridge-upgrade was at commit dbee7e9f2, tracking origin/feat/toolkit-bridge-upgrade; preceding commits were 723375b6c (fix(cli): address upgrade review findings), 9c874298e (fix(cli): address toolkit bridge review), and 04867eaf9 (feat(cli): add toolkit upgrade bridge).
• 🔴 (00:25) The toolkit bridge upgrade diff modified 16 files with exactly 1,663 insertions and 301 deletions: packages/cli/src/commands/cli/upgrade.ts, packages/cli/src/lib/binary.ts, packages/cli/src/lib/delta-upgrade.ts, packages/cli/src/lib/ghcr.ts, packages/cli/src/lib/release-notes.ts, packages/cli/src/lib/upgrade.ts, packages/cli/src/lib/version-check.ts, packages/cli/test/commands/cli.test.ts, packages/cli/test/commands/cli/upgrade.test.ts, packages/cli/test/lib/binary.test.ts, packages/cli/test/lib/delta-upgrade.mocked.test.ts, packages/cli/test/lib/delta-upgrade.test.ts, packages/cli/test/lib/ghcr.test.ts, packages/cli/test/lib/release-notes.test.ts, packages/cli/test/lib/upgrade.test.ts, and packages/cli/test/lib/version-check.test.ts.
• 🟡 (00:25) Review workflow status: 1. repository guidance, clean state, and exact base/head revisions verified (completed); 2. complete base-to-head diff and every changed file enumeration/inspection in progress; 3. tracing security and supply-chain invariants through surrounding code/tests pending; 4. immutable revision/state re-verification and structured verdict pending.
• 🔴 (00:25) User stated package-manager upgrades always require network access to fetch and install packages; therefore offline upgrade mode is supported only for curl-installed binaries, and validateMethod() throws UpgradeError("unsupported_operation", "Offline upgrade is only supported for curl-installed binaries.") when offline is used with a method other than "curl".
• 🔴 (00:25) User stated nightly builds are GitHub-only, so pinned nightly-version validation must always use the "curl" GitHub lookup regardless of the current installation method; lookupMethod is selected as channel === "nightly" ? "curl" : method.
• 🔴 (00:25) The upgrade command imports and uses source-aware resolution through UpgradeSource, resolveExistingUpgradeVersion, and resolveLatestUpgradeVersion; check results can include source: latestResolution?.source.
• 🔴 (00:25) sentry cli upgrade nightly means “Switch to nightly channel and update.”
• 🔴 (00:25) Upgrade method validation rejects a specific stable version with Homebrew and directs users to brew upgrade getsentry/tools/sentry; Homebrew version pinning is unsupported because versioning is managed through the formula.
• 🔴 (00:25) Migration warnings tell users that an existing package-manager-installed sentry may still appear earlier in PATH; uninstall hints are npm uninstall -g sentry, pnpm remove -g sentry, bun remove -g sentry, yarn global remove sentry, and brew uninstall getsentry/tools/sentry.
• 🔴 (00:26) User stated trailing path separators should be stripped for path comparison, but never from a bare root such as /; stripTrailingSep(p) returns p.slice(0, -1) only when p.length > 1 && p.endsWith(sep).
• 🔴 (00:26) Legacy migration sources are deliberately restricted to pre-XDG ~/.sentry/bin through LEGACY_INSTALL_SUBDIR and LEGACY_INSTALL_SUBDIRS; ~/.local/bin and ~/bin remain valid current XDG install targets and must not be treated as migration sources.
• 🔴 (00:26) Linux musl detection in packages/cli/src/lib/binary.ts uses two ordered heuristics: 1. check /lib/ld-musl-<arch>.so.1; 2. run ldd --version and inspect combined stdout/stderr for "musl". The result is cached, and failure to run ldd falls back to glibc (false).
• 🔴 (00:26) Binary release URL construction became source-aware: getBinaryDownloadUrl(version, source = PRIMARY_UPGRADE_SOURCE) uses ${source.tagPrefix}${version} and https://github.com/${source.githubRepo}/releases/download/${tag}/${getPlatformBinaryName()}.
• 🔴 (00:26) Source-aware GitHub helpers added in packages/cli/src/lib/binary.ts: getGitHubReleasesUrl() builds https://api.github.com/repos/${source.githubRepo}/releases; getGitHubReleaseByTagUrl() appends /tags/${encodeURIComponent(tag)}; getGitHubLatestReleaseUrl() uses ?per_page=100 when source.tagPrefix is present and /latest otherwise.
• 🔴 (00:26) User stated a successful source/repository probe response is returned to the caller so the caller never repeats the request.
• 🔴 (00:26) Nightly versions are recognized by isNightlyVersion(version) when the version includes "-dev."; the documented nightly format is X.Y.Z-dev.<unix-seconds>.