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

Ouverte
  • Quelque chose ne va pas ?
#5,463 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github-actions, typescript
Domaine
ci-cd, devtools

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

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.

Langage dominant
TypeScript
Étoiles
91.7k
Forks
11.9k
Merge moyen
3 h 30 min
PR mergées (30 j)
199

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de modelcontextprotocol/servers

Toutes les issues de modelcontextprotocol/servers

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.