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

release skill 4d: document the ledger's title, layout and required sections

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#5,343 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
78/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
documentation

Línea de trabajo

Edita el paso 4d, «The ledger», en .claude/skills/release/SKILL.md. Lee la sección existente y el título, el diseño, las secciones obligatorias, las columnas de la tabla, las pastillas de estado y las indicaciones sobre el segundo PR de merge que solicita el issue; asegúrate de que se especifique cada elemento y se mantengan los requisitos existentes. La tarea estará terminada cuando el paso incluya todos los detalles solicitados y npm run verify:skills se ejecute correctamente.

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

Descripción

documentation v2

Problem

Release skill step 4d (.claude/skills/release/SKILL.md, "The ledger") lists what a release ledger must contain: the masthead, verdict, gate cells, packaging table, what will publish, one table per theme, and findings. It says nothing about how the ledger is titled or laid out, or about building on the previous one. The v2.0.0, v2.1.0 and v2.2.0 ledgers share one design only because each was copied from the last by hand. The only record of that is a CSS comment in the page ("Same system as the v2.0.0 ledger"), and a session that doesn't know about it builds a different page.

The last two ledgers also carry sections step 4d doesn't ask for, which were the useful ones:

  • SDKs and Toolchain lines in the masthead: the MCP SDK versions locked, and the Node, uv, Inspector, Playwright, Docker and Claude Code versions used.
  • Preparation PRs: the audit (or its report, when no fix was forced), Version Packages and Prepare Python Release, each with what was checked.
  • Tool schemas against the previous release: each TypeScript server's tools/list (input and output schemas, annotations, descriptions) against the versions the previous release published, in both eras.
  • LLM client: one headless Claude Code run (--strict-mcp-config) calling one tool on each of the seven release-candidate builds.
  • Also shipping: advisory fixes: fixes that shipped through an advisory and not a milestone issue.

Proposal

Amend step 4d so that it:

  1. Titles the page Servers vX.Y.Z Release Ledger, for both the <title> and the <h1>.
  2. Starts from the previous release's ledger, which is linked from the latest published Release's notes ("Release ledger: …"). It reuses that page's stylesheet and section structure, changing content only. The skill links to the previous Release rather than naming an artifact URL, so it never holds a link that goes stale.
  3. Lists the five sections above as required, alongside the existing ones.
  4. Names the issue-table columns: Issue · Title · What was driven · Observed · Status. Each Issue cell is tagged client, web UI or probe, and each Status is a pill (PASS, or a named exception).
  5. Covers a second merge PR. When a fix lands after the first merge PR (v2.2.0 needed #5342 after #5338 for the certifi lockfile), the masthead names both merge PRs, and the page says which checks ran on which head and what differs between the two trees.

Done when

.claude/skills/release/SKILL.md step 4d says all of the above, and npm run verify:skills passes. The release skill is name-only (disable-model-invocation: true), so no eval cases change.

Lenguaje dominante
TypeScript
Estrellas
91.6k
Forks
11.9k
Merge medio
4 h 31 min
PR fusionados (30 d)
236

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/servers

Todos los issues de modelcontextprotocol/servers

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.