toolkit merge: pre-rename validation, rename, release cutover

Open
#1,246 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, typescript
Domain
build-system, ci-cd, cloud, devops, release

Research direction

This is an umbrella cutover task spanning the linked CLI and MCP issues; start by reading getsentry/cli#1239, getsentry/sentry-mcp#1156, and getsentry/cli#1244. Use the checklist as the validation plan, including apps/cli-docs and the listed pnpm checks. Done means the rename, canaries, staging releases, dual publishing, and compatibility window are completed without archiving getsentry/cli early.

Written by the indexing model from the issue text.

Description

Sub-task of the toolkit monorepo merge: getsentry/cli#1248.

Pre-rename validation in getsentry/sentry-mcp

  • Import CLI and docs under the current repository name: getsentry/cli#1239.
  • Full pnpm build, typecheck, lint, test:unit, test:e2e, MCP evals/smoke, CLI binary smoke on all platforms, and docs preview pass.
  • Workspace Publish dry-runs pass for CLI and MCP.
  • Prefixed Craft workspace dry-runs pass for CLI and MCP with no cross-product tag/changelog/version contamination.
  • Existing MCP Cloudflare Worker deploy canary passes after Turbo removal.
  • Release-gated Cloudflare CLI-docs preview passes from apps/cli-docs, with https://cli.sentry.dev/install unchanged.
  • Independent correctness and security reviews pass on the exact integration head.

Rename and post-rename validation

  • Rename getsentry/sentry-mcp -> getsentry/toolkit: getsentry/sentry-mcp#1156.
  • Verify redirects, settings, secrets, environments, GitHub App, webhooks, branch protections, and Cloudflare wiring.
  • Rerun the full CI and deployment canaries under the new repository name.
  • Publish one staging CLI release and one staging MCP release from Toolkit.
  • Run the full CLI upgrade compatibility matrix: getsentry/cli#1244.

Cutover

  • Start dual-publishing CLI stable releases and nightlies to both Toolkit and getsentry/cli.
  • Announce Toolkit as the canonical repository.
  • Keep getsentry/cli writable and its releases/GHCR live throughout the compatibility window.
  • After at least two stable releases and roughly 90 days of verified compatibility, archive getsentry/cli with a README redirect.

The old CLI repository must never be archived before dual publishing ends.

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
22h 3m
Merged PRs (30d)
94

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.