CI: rename everything-mcp-diff.yml to mcp-interface-diff.yml, staged across a milestone merge

Open
  • Is something wrong?
#5,463 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, typescript
Domain
ci-cd, devtools

Research direction

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.

Written by the indexing model from the issue text.

Description

chore v2

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:

  1. Add mcp-interface-diff.yml beside the old file, with the callers unchanged, and ship it to main in a milestone merge. Make sure only one of the two runs on push / pull_request (for example, the new file is workflow_dispatch-only until step 2).
  2. After that merge, point both dispatch loops, gh run list --workflow, TOOLING_PATHS in scripts/lib/interface-diff-servers.mjs, scripts/version-pr-ci.test.mjs, RELEASING.md, the release skill, docs/quality-gate.md and the AGENTS.md tree at the new file, give it the full triggers, and delete the old one.

Related: #5428, #5459.

Dominant language
TypeScript
Stars
91.7k
Forks
11.9k
Avg merge
3h 30m
Merged PRs (30d)
204

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/servers

All issues in modelcontextprotocol/servers

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.