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

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

Chiusa Adatta ai principianti
  • Qualcosa non va?
#5,343 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
78/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
documentation

Direzione di ricerca

Modifica il passaggio 4d, «The ledger», in .claude/skills/release/SKILL.md. Leggi la sezione esistente e il titolo, il layout, le sezioni obbligatorie, le colonne della tabella, gli indicatori di stato e le indicazioni sulla seconda PR di merge richiesti dall’issue; assicurati che ciascun elemento sia specificato e che i requisiti esistenti siano mantenuti. Il lavoro è terminato quando il passaggio include tutti i dettagli richiesti e npm run verify:skills viene eseguito correttamente.

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

Descrizione

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.

Lingua principale
TypeScript
Stelle
91.6k
Fork
11.9k
Merge medio
4h 31m
PR unite (30g)
236

Preparare l'ambiente

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

Tutte le issue di modelcontextprotocol/servers

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.