Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

chore(deps): upgrade the MCP TypeScript SDK to 2.2.0

Abierto
  • ¿Algo no está bien?
#2,521 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
75/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
build-system, tooling

Línea de trabajo

Start with the repo-root package.json and the MCP TypeScript SDK release notes; confirm the four pinned packages move together, then run npm install to refresh the lockfile. Re-check clients/cli/tsup.config.ts, clients/tui/tsup.config.ts, and clients/web/tsup.runner.config.ts if entry points changed, then run npm run format, npm run verify:bundle-externals, and npm run local:gate.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

chore dependencies v2

A new MCP TypeScript SDK release is out. What is installed on v2/main is behind what the npm registry publishes.

Package Declared Installed on v2/main Latest on npm Behind
@modelcontextprotocol/client 2.1.0 2.1.0 2.2.0 yes
@modelcontextprotocol/core 2.1.0 2.1.0 2.2.0 yes
@modelcontextprotocol/server 2.1.0 2.1.0 2.2.0 yes
@modelcontextprotocol/server-legacy 2.1.0 2.1.0 2.2.0 yes

Release notes: https://github.com/modelcontextprotocol/typescript-sdk/releases

Why this is an issue and not a PR

Filed by the nightly SDK watch (#1063), the third of this repo's issue-filing sweeps alongside the monthly dependency refresh (#2229) and the daily Dependabot alert sweep (#2233). None of them opens a PR: a bot-authored PR carries no Closes #N and no board card, so the work would be invisible to the board. A maintainer picks this up and opens a normal PR against v2/main.

Upgrade checklist
  • Bump the version(s) in the repo-root package.json — every runtime dependency core/ imports is declared in the repo-root package.json and nowhere else (Dependency placement). The four typescript-sdk packages are pinned exactly, so they move together.
  • npm install at the root, and commit the refreshed lockfile.
  • Re-check the bundler external lists (clients/{cli,tui}/tsup.config.ts, clients/web/tsup.runner.config.ts) if the release adds or renames an entry point; npm run verify:bundle-externals enforces this against the built output.
  • npm run format, then npm run local:gate.

An automated review of what actually changed upstream — and which parts of this app it touches — is posted as a comment below.

A later run of this sweep will not refile this issue. A further SDK release files its own issue and leaves a supersession note here rather than editing this one.

Lenguaje dominante
TypeScript
Estrellas
11k
Forks
1.5k
Merge medio
5 h 18 min
PR fusionados (30 d)
130

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modelcontextprotocol/inspector

Todos los issues de modelcontextprotocol/inspector

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.