CI: rename everything-mcp-diff.yml to mcp-interface-diff.yml, staged across a milestone merge
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, typescript
调研方向
Start by reading .github/workflows/everything-mcp-diff.yml and the two version workflows, version-packages.yml and prepare-python-release.yml, to trace their dispatch calls and triggers. Then review scripts/lib/interface-diff-servers.mjs, scripts/version-pr-ci.test.mjs, RELEASING.md, docs/quality-gate.md, the release skill and the AGENTS.md tree listed in the issue. Done when the staged rename preserves the dispatched diff across the milestone merge, updates all references, and only one workflow runs on push and pull requests.
由索引模型根据 Issue 内容生成。
描述
Problem
.github/workflows/everything-mcp-diff.yml diffs every server's MCP interface since #5459 (#5428), but its file name still says everything. #5459 renamed it to mcp-interface-diff.yml at first, and backed that out after review: GitHub dispatches a workflow only when its file exists on the default branch (main). Both version workflows (version-packages.yml, prepare-python-release.yml) dispatch it by file name from v2/main, so a one-step rename on v2/main breaks their dispatch until the next milestone merge, and the first version PR after it gets no Interface diff (dispatched) status.
Expected behavior
The workflow file is named for what it does (mcp-interface-diff.yml), and version PRs keep their dispatched diff throughout the transition.
Notes for the implementation
Stage the rename across a milestone merge:
- Add
mcp-interface-diff.ymlbeside the old file, with the callers unchanged, and ship it tomainin a milestone merge. Make sure only one of the two runs onpush/pull_request(for example, the new file isworkflow_dispatch-only until step 2). - After that merge, point both dispatch loops,
gh run list --workflow,TOOLING_PATHSinscripts/lib/interface-diff-servers.mjs,scripts/version-pr-ci.test.mjs,RELEASING.md, thereleaseskill,docs/quality-gate.mdand theAGENTS.mdtree at the new file, give it the full triggers, and delete the old one.
Related: #5428, #5459.
- 主要语言
- TypeScript
- 星标
- 91.7k
- 派生
- 11.9k
- 平均合并
- 3 小时 30 分钟
- 30 天内合并 PR
- 204
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/servers 的其他 Issue
-
bug v2
难度 1/5 1 小时以内 新手友好度 88/100
modelcontextprotocol/servers#5483 ·
维护者通常 1 天内回复
-
bug v2
难度 2/5 1-3 小时 新手友好度 65/100
modelcontextprotocol/servers#5482 ·
维护者通常 1 天内回复
-
chore dependencies server-filesystem v2
难度 2/5 1-3 小时 新手友好度 78/100
modelcontextprotocol/servers#5481 · 1 条评论 ·
维护者通常 1 天内回复
-
bug server-filesystem v2
难度 5/5 一周以上 新手友好度 25/100
modelcontextprotocol/servers#5260 · 3 条评论 ·
维护者通常 1 天内回复
-
git: the string "null" for base_branch, contains or not_contains arrives as None (python-sdk#3055)未关闭bug server-git v2 waiting-on-sdk
难度 3/5 1-2 天 新手友好度 68/100
modelcontextprotocol/servers#5176 · 1 条评论 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/servers 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
shoelace-style/webawesome#2979 ·
维护者通常 1 天内回复
-
Chip source filter and denial markers miss Storage rows when a Storage activity source is picked未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
omdsh-dev/DSH-better-sidebar#1141 ·
维护者通常 2 天内回复