release skill 4d: document the ledger's title, layout and required sections
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 78/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
编辑 .claude/skills/release/SKILL.md 中的步骤 4d“账本”。阅读现有章节，以及 issue 要求的标题、布局、必需章节、表格列、状态标签和第二个 merge PR 的指导；确保每项都有说明，同时保留现有要求。步骤涵盖所有要求的细节且 npm run verify:skills 通过后，即告完成。
由索引模型根据 Issue 内容生成。
描述
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:
- Titles the page
Servers vX.Y.Z Release Ledger, for both the<title>and the<h1>. - 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.
- Lists the five sections above as required, alongside the existing ones.
- Names the issue-table columns: Issue · Title · What was driven · Observed · Status. Each Issue cell is tagged
client,web UIorprobe, and each Status is a pill (PASS, or a named exception). - Covers a second merge PR. When a fix lands after the first merge PR (v2.2.0 needed #5342 after #5338 for the
certifilockfile), 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.
- 主要语言
- TypeScript
- 星标
- 91.6k
- 派生
- 11.9k
- 平均合并
- 4 小时 31 分钟
- 30 天内合并 PR
- 236
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/servers 的其他 Issue
-
enhancement server-everything v2
难度 2/5 1-3 小时 新手友好度 72/100
modelcontextprotocol/servers#5371 · 1 条评论 ·
维护者通常 1 天内回复
-
chore server-filesystem server-memory server-sequentialthinking v2
难度 2/5 1-3 小时 新手友好度 78/100
modelcontextprotocol/servers#5345 ·
维护者通常 1 天内回复
-
docs(git): clarify unconfined default scope and repository confinement options in README and CLI未关闭documentation server-git v2
难度 1/5 1 小时以内 新手友好度 74/100
modelcontextprotocol/servers#5230 · 1 条评论 ·
维护者通常 1 天内回复
-
bug server-filesystem v2
难度 2/5 1-3 小时 新手友好度 72/100
modelcontextprotocol/servers#5216 · 3 条评论 ·
维护者通常 1 天内回复
-
documentation server-git server-time v2
难度 2/5 1-3 小时 新手友好度 72/100
modelcontextprotocol/servers#5213 · 2 条评论 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/servers 的全部 Issue
相似的 Issue
-
bug triage
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
hemi-earn
难度 2/5 1-3 小时 新手友好度 82/100
vetro-protocol/vetro-monorepo#1043 ·
维护者通常 1 天内回复
-
stage 2: bare names resolve against PATH differently from the shell (empty and relative entries)未关闭
难度 2/5 1-3 小时 新手友好度 82/100
STRML/omp-classifier#206 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
atlassian-labs/mermaid-diagrams-viewer#188 ·
维护者通常 1 天内回复
-
dashboard enhancement
难度 2/5 1-3 小时 新手友好度 76/100
Olanetsoft/agent-lookout#225 ·
维护者通常 1 天内回复