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

Aperta
  • Qualcosa non va?
#5,463 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, typescript
Ambito
ci-cd, devtools

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
TypeScript
Stelle
91.7k
Fork
11.9k
Merge medio
3h 30m
PR unite (30g)
204

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.