Merge sentry-cli + sentry-mcp into getsentry/toolkit monorepo (master)

[BYK]

Tracking issue for merging getsentry/cli into the existing getsentry/sentry-mcp repository, validating the combined monorepo there, and only then renaming it to getsentry/toolkit. The final repository is a pnpm workspace (no Turbo) with independent prefixed releases and phased shared code.

Full plan: https://gist.github.com/BYK/8c0ce6cec64608f41fe5654b7827228e

Settled architecture

• Use getsentry/sentry-mcp as the destination; do not create a fresh repository. This preserves MCP production secrets, environments, GitHub App, webhooks, Vercel, and Cloudflare wiring.
• Import CLI while the repository is still named getsentry/sentry-mcp. Rename only after the integrated monorepo and live deployment paths pass every gate.
• Preserve CLI and docs history through two filtered git subtree imports into packages/cli and apps/cli-docs.
• Release products independently with cli@x.y.z and mcp@x.y.z.
• CLI docs and previews use release-gated Vercel at https://cli.sentry.dev; keep https://cli.sentry.dev/install unchanged. The earlier Cloudflare-docs proposal is superseded. The MCP Worker remains on Cloudflare.
• Drop Turbo for pnpm-native orchestration.
• Manage patches at the workspace root and use a shared dependency catalog.
• Colocate first; extract @sentry/toolkit-core later.

Ordered migration gates

1. Prerequisites

• toolkit merge: pre-shape CLI into packages/cli + apps/cli-docs #1238 / chore: pre-shape repo into pnpm-workspace monorepo layout #1254 — pre-shape CLI into packages/cli and apps/cli-docs.
• feat: accept workspace publish requests publish#9339 — accept workspace publish requests.
• fix: bootstrap root publish locations publish#9456 — bootstrap root publish locations.
• feat: prefix-aware read paths for monorepo multi-product releases craft#847 — prefix-aware tag and changelog read paths.
• feat(config): top-level workspaces schema + --workspace selector craft#848 — top-level release workspace schema and selector.
• feat: propagate release workspaces craft#872 — propagate release workspaces.
• Keep the working release-gated Vercel CLI-docs hosting and previews.

2. Bridge CLI release — hard blocker

• toolkit merge: bridge CLI release + dual-source upgrade compatibility #1244 / feat(cli): add toolkit upgrade bridge #1569 — implement ordered Toolkit-first / CLI-fallback upgrade sources.
• Cut and verify stable bridge CLI release 0.45.0 from getsentry/cli; import is now unblocked.

3. Import and integrate under the current name

• toolkit merge: import CLI into sentry-mcp, validate, then rename #1239 — imported CLI and docs history into getsentry/sentry-mcp before the rename (Toolkit #1320).
• Adopt pnpm 11, Biome 2, a shared dependency catalog, and root patchedDependencies declarations (toolkit merge: unify toolchain + root patches (bump @sentry/* to 10.54.0) #1240).
• toolkit merge: unify toolchain + root patches (bump @sentry/* to 10.54.0) #1240 — reconcile the root Node >=22.13 engine with the planned >=22.15 requirement, the CLI's deliberate-or-not Sentry 10.63 pin versus the 11.1 catalog, and the root linker/patch-layout policy.
• Replace Turbo with pnpm-native root builds, workspace filters, and the verified MCP production build/deploy path (toolkit merge: drop Turbo, pnpm-native orchestration #1241, Toolkit #1400).
• toolkit merge: drop Turbo, pnpm-native orchestration #1241 — finish or explicitly descope incremental TypeScript project references across the remaining workspaces; Cloudflare has references, but CLI does not.
• Ship metadata-discovered changed-workspace CI, skip-aware required test, packaged-CLI runtime jobs, and five-platform Toolkit GHCR nightly (toolkit merge: per-product CI with changed-file gating #1242, Toolkit #1393).
• toolkit merge: per-product CI with changed-file gating #1242 — reconcile the originally requested MCP deploy path filter with the current successful-Test-on-main deployment trigger; do not silently change production deployment behavior.
• Configure product-selected Craft workspaces and publish prefixed cli@0.46.0 and cli@0.47.0 releases (toolkit merge: independent CLI releases and continuous MCP deployment #1243).
• The MCP Worker deploys continuously after a successful main-branch Test through the protected exact-version workflow (feat(docs): add Vercel analytics and speed insights #1399, docs: weekly documentation audit — fix Zod→Valibot drift, stale versions, dataset list #1400). A separate mcp@ GitHub release is not a production-deployment gate; stdio npm package releases remain available through the MCP Craft workspace when needed.

4. Pre-rename validation

• toolkit merge: pre-rename validation, rename, release cutover #1246 — reconcile historical CLI/MCP CI, workspace release dry-runs, Vercel CLI-docs preview, and MCP Cloudflare deploy evidence under the former repository name.
• Independent correctness and security reviews passed on the exact CLI import head (Toolkit #1320).

5. Rename and revalidate

• Renamed the imported repository to getsentry/toolkit, retaining repository ID 957245447; verified exact-version MCP production deployment and post-rename CI (Toolkit #1399, #1400).
• Validate merged monorepo in sentry-mcp, then rename to getsentry/toolkit toolkit#1156 — finish the remaining redirect, GitHub App, webhook, protection, and repository-reference audit before closing the rename tracker.
• Published Toolkit CLI stable 0.46.0 and 0.47.0 and verified the legacy-to-Toolkit Linux x64 upgrade chain (cutover evidence).
• Match the old CLI CI platform smoke coverage and reconcile the remaining upgrade-source cases (toolkit merge: bridge CLI release + dual-source upgrade compatibility #1244); an mcp@ release is not required for MCP Worker deployment.

6. Cutover and compatibility window

• Verified Toolkit stable and nightly artifacts, the live stable/nightly installer, npm on Node 20/22/24, and Linux x64 legacy 0.44.1 -> bridge 0.45.0 -> Toolkit stable 0.47.0 -> Toolkit nightly -> stable (cutover evidence).
• Finish any required non-Linux and package-manager/Homebrew end-to-end compatibility checks before declaring distribution cutover complete; keep legacy bridge assets readable for older binaries.
• Announce Toolkit as canonical.
• Keep getsentry/cli writable; do not archive it while dual publishing is active.
• After open PRs/issues are migrated in the dedicated session and the distribution/upgrade cutover passes, archive getsentry/cli promptly with a README redirect. No fixed dual-publishing period is required.

7. Follow-up

• Keep release-gated CLI docs and previews on Vercel, preserving https://cli.sentry.dev/install. Cloudflare remains the MCP Worker host.
• Toolkit #1402 — publish trusted JUnit/coverage results and finish the separate CI-reporting hardening left from closed fix(local): warn when the event stream cannot be attached #1343.
• toolkit merge: Phase B — extract @sentry/toolkit-core (shared code) #1247 — extract @sentry/toolkit-core incrementally.

Highest risks

• toolkit merge: bridge CLI release + dual-source upgrade compatibility #1244: compatibility for old binaries that only know getsentry/cli.
• toolkit merge: drop Turbo, pnpm-native orchestration #1241 / Validate merged monorepo in sentry-mcp, then rename to getsentry/toolkit toolkit#1156: changes to the live MCP deploy path and repository identity.

The import and rename already happened in that order. Never archive getsentry/cli before PR/issue migration and the distribution/upgrade cutover finish.

[BYK]

Bridge gate complete: #1569 shipped as stable CLI 0.45.0 through getsentry/publish#9491. Pre-bridge legacy upgrade, Toolkit-404/legacy fallback from the bridge binary, live installer, GitHub/npm artifact identity, Homebrew checksums, registry metadata, and release deployment were verified. #1239 is now unblocked; detailed evidence is recorded on #1239.

[BYK]

Cutover update (2026-10-05): Toolkit already contains the history-preserving CLI import (#1320), was renamed from getsentry/sentry-mcp, uses pnpm-native root scripts and workspace-aware CI, publishes a prefixed cli@0.46.0 release and public five-platform Toolkit GHCR nightly, and has a verified exact-version MCP production deployment (#1399, #1400). The reviewed nightly shell-installer cutover is now getsentry/toolkit#1403. The user confirmed that the working, release-gated Vercel CLI-docs target is final; the older Cloudflare-docs migration checkbox is superseded. Stale deployment/journal PR getsentry/toolkit#1343 is closed; its distinct unfinished CI report publication is tracked in getsentry/toolkit#1402.

Keep this tracker open for the remaining migration gates: exact-head review/merge of #1403; product release and upgrade compatibility matrix (including proving both stable channels dual-publish); legacy open PR/issue triage and reference cleanup; and the observed period of at least two stable releases and roughly 90 days before retiring getsentry/cli. Do not archive legacy or treat stale unchecked import/rename boxes as evidence that those already-completed steps need redoing.

[BYK]

Cutover update (2026-10-05): Toolkit CLI 0.47.0 is published from a checked candidate; npm, five platform binaries, the release registry, and the live Vercel /install artifact were verified. The live installer now uses Toolkit GHCR for nightly, installs stable 0.47.0 by default, and falls back to the legacy exact tag only on Toolkit 404. In isolated Linux x64 installs, legacy 0.44.1 → bridge 0.45.0 → Toolkit 0.47.0 works; 0.47.0 → Toolkit nightly → stable 0.47.0 works too. Installed stable binaries matched published SHA-256 assets. Full run links, hashes, and test boundaries: #1246 verification.

The user is handling the legacy open-PR/issue migration in a separate session. Once that finishes and public legacy bridge artifacts remain reachable by old clients, archive getsentry/cli promptly with a README redirect; the old two-release/90-day waiting rule is superseded. The working Vercel docs site is transitional: the chosen final CLI-docs target is release-gated Cloudflare hosting and previews, preserving https://cli.sentry.dev/install. That hosting move is separate from the legacy-repository retirement gate. Historical unchecked import/rename boxes do not undo the completed import and rename.