Link the released 2026-07-28 spec and point migrators at /v1/
Merged
MA
3mo ago+6+6+0123456789-1-1-0123456789
Two small link fixes in the v2-facing docs.
Motivation and Context
The README banner linked the spec's release-candidate blog post; the 2026-07-28 specification is published now, so link it directly. The migration guide's "Need Help?" section also gets the same pointer to the v1.x maintenance-line docs (/v1/) that index.md and whats-new.md already carry.
How Has This Been Tested?
Link targets checked (spec URL returns 200).
Breaking Changes
None.
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
- Documentation update
Checklist
- I have read the MCP Documentation
- My code follows the repository's style guidelines
- New and existing tests pass locally
- I have added appropriate error handling
- I have added or updated documentation as needed