Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#1,248 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, typescript
Ambito
build-system, ci-cd, cloud, release

Direzione di ricerca

Inizia con il piano di migrazione collegato e il lavoro in sospeso in #1239–#1243, che riguardano l’importazione della CLI, l’unificazione del tooling, la sostituzione di Turbo, il gating della CI e i workspace di release. Il lavoro è completato quando l’integrazione sequenziale, la validazione pre-rinomina, i canary di deployment e i requisiti di compatibilità di questa issue sono stati superati prima di qualsiasi rinomina del repository.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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 [email protected] and [email protected].
  • CLI docs and previews are release-gated on Cloudflare; https://cli.sentry.dev/install remains unchanged. 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
  • #1238 / getsentry/cli#1254 — pre-shape CLI into packages/cli and apps/cli-docs.
  • getsentry/publish#9339 — accept workspace publish requests.
  • getsentry/publish#9456 — bootstrap root publish locations.
  • getsentry/craft#847 — prefix-aware tag and changelog read paths.
  • getsentry/craft#848 — top-level release workspace schema and selector.
  • getsentry/craft#872 — propagate release workspaces.
  • Replace the transitional Vercel CLI-docs target with release-gated Cloudflare hosting and previews.
2. Bridge CLI release — hard blocker
  • #1244 / #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
  • #1239 — import CLI and docs history into an integration branch of getsentry/sentry-mcp.
  • #1240 — unify toolchain, dependency catalog, and root patches.
  • #1241 — replace Turbo with pnpm-native orchestration.
  • #1242 — per-product CI and changed-file gating.
  • #1243 — configure prefixed independent release workspaces.
4. Pre-rename validation
  • #1246 — full CLI/MCP CI, workspace release dry-runs, Cloudflare CLI-docs preview, and MCP Cloudflare deploy canary pass under getsentry/sentry-mcp.
  • Independent correctness and security reviews pass on the exact integration head.
5. Rename and revalidate
  • getsentry/sentry-mcp#1156 — rename to getsentry/toolkit, verify all repository and deployment integrations, rerun CI and canaries.
  • Run staging releases for both products and the complete CLI compatibility matrix.
6. Cutover and compatibility window
  • Dual-publish CLI releases and nightlies to Toolkit and getsentry/cli.
  • Announce Toolkit as canonical.
  • Keep getsentry/cli writable; do not archive it while dual publishing is active.
  • After at least two stable releases and roughly 90 days, verify legacy usage has ended, then archive getsentry/cli with a redirect.
7. Follow-up
  • #1247 — extract @sentry/toolkit-core incrementally.

Highest risks

  • #1244: compatibility for old binaries that only know getsentry/cli.
  • #1241 / getsentry/sentry-mcp#1156: changes to the live MCP deploy path and repository identity.

Every gate is sequential. Never rename before pre-rename validation, and never archive getsentry/cli before the compatibility window ends.

Lingua principale
TypeScript
Stelle
123
Fork
14
Merge medio
23h 23m
PR unite (30g)
82

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di getsentry/cli

Tutte le issue di getsentry/cli

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.