go-live 9/9: write the v1 to v2 migration guide #1822

Activity

1. cliffhall

   self-assigned this

   on Jul 27, 2026
2. cliffhall

   added

   v2Issues and PRs for v2Issues and PRs for v2

   on Jul 27, 2026
3. cliffhall

   changed the title [-]go-live 8/9: post-swap docs, labels, boards, and integration hygiene[/-] [+]go-live 9/9: write the v1 to v2 migration guide[/+] on Jul 27, 2026
4. cliffhall

   added a parent issue on Jul 28, 2026

   • Remove the probe-era auth-challenge workaround and detect the SDK's typed 401/403 #1807
5. cliffhall

   removed a parent issue on Jul 28, 2026

   • Remove the probe-era auth-challenge workaround and detect the SDK's typed 401/403 #1807
6. cliffhall

   added a parent issue on Jul 28, 2026

   • plan: v2 go-live runbook — deprecate v1 (1.0.1), branch v1/main, swap main to v2, publish 2.0.0, close v1 backlog, restrict external PRs #1804
7. cliffhall

   added this to the v2.2.0 milestone on Jul 28, 2026
8. cliffhall commented on Aug 1, 2026

   

   cliffhall

   on Aug 1, 2026

   Last edited by cliffhall

   MemberAuthor

   More actions

   Triage: Priority = High

   Scored 9/16 with the priority rubric added to AGENTS.md in #1891. This card is already approved and sitting in Todo — only Priority was set here, its Status is unchanged.

   Axis	Score	Reasoning
   Severity / impact	3/5	A docs gap rather than a defect, but a consequential one: CLI flags changed substantially and --config semantics genuinely differ in v2, so the deprecation notice currently sends people somewhere confusing with no map.
   Urgency / staleness	4/5	The trigger already fired — v2 is published and v1 is deprecated — so the guide is late relative to the event it was meant to accompany, and the #1872 sweep has just pointed 135 reporters at v2.
   Signal bonuses	+2	milestone (v2.2.0) (+1), assigned (+1)
   Total	9	Lands in the High band (9-11).

   Related issues. These look connected and may be worth reading together:

   • Execute the first v2/main → main milestone merge and cut the release #1876 — the release this guide was scoped to ship alongside
   • docs: new modelcontextprotocol.io Inspector documentation for v2 (legacy vs. modern era, more screenshots) #1803 — the paired documentation work for modelcontextprotocol.io
   • Triage the open issue backlog: backfill v1/v2 labels, close legacy, board the rest #1872 — the deprecation sweep that just directed a large group of v1 users toward v2

   Scores are a starting point, not a verdict — the rubric is meant to be overruled when it's plainly wrong, provided the reason is written down.
9. cliffhall

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Aug 5, 2026
10. cliffhall

    linked a pull request that will close this issuedocs: add the v1 → v2 migration guide #1960on Aug 11, 2026
11. cliffhall

    closed this as completedon Aug 11, 2026
12. olaservo

    added a commit that references this issue on Aug 11, 2026

    docs: add the v1 → v2 migration guide

    ...

    This issue will close once commit 2e89443 is merged into the 'main' branch.

    2e89443