Skip to content

docs: add redirects for restructured spec pages#3065

Open
claude[bot] wants to merge 1 commit into
docs/2026-07-28-releasefrom
claude/rc-nav-redirects
Open

docs: add redirects for restructured spec pages#3065
claude[bot] wants to merge 1 commit into
docs/2026-07-28-releasefrom
claude/rc-nav-redirects

Conversation

@claude

@claude claude Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Requested by Den Delimarsky · Slack thread

Following an old link such as /specification/draft/basic/utilities/progress used to land on a 404 page after the draft spec restructure. Those URLs now redirect to the pages that carry the content, for example the cancellation and progress pages under basic/patterns and the tasks extension overview. The same redirects exist for the 2026-07-28 dated paths, so latest URLs will keep resolving once the release flip repoints them.

Motivation and Context

Preparation for the 2026-07-28 release. The draft spec restructure moved the cancellation and progress utilities under basic/patterns and folded lifecycle into versioning. It also removed the ping utility (SEP-2575) and moved tasks into the io.modelcontextprotocol/tasks extension (SEP-2663). docs.json had no redirects for the old URLs, so bookmarks and inbound links broke. The draft nav blocks already register all 32 draft pages, so only redirects were needed. The future redirects are keyed on dated /specification/2026-07-28/... sources rather than latest sources, so they stay inert until the release flip repoints the latest wildcard, matching the existing dated-source precedent in the file.

Closes #3052

How Has This Been Tested?

Documentation-only change. Ran npm install and npm run check:docs, which passed. That includes the prettier check on md/mdx files and mint broken-links, which reported no broken links.

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

Additional context

Other rc-high-priority bundle PRs also touch docs/docs.json, so merge order may need care.

AI assistance disclosure: this change and the PR description were written with AI assistance, which also ran the lint checks above. The diff will receive human review before merge.

The draft spec deletes basic/lifecycle and basic/utilities/ping, moves
cancellation and progress under basic/patterns/, and moves tasks out of
the core protocol into an extension. Add redirects for the old paths in
two forms: draft-scoped sources that work now, and 2026-07-28-scoped
sources that take effect once the /specification/latest wildcard points
at 2026-07-28.

Removed pages point at their closest replacement: lifecycle goes to
versioning, ping goes to the changelog entry recording its removal, and
tasks goes to the tasks extension overview.

The draft nav already lists every restructured page, so no nav changes
were needed.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016WBaED7Rta4YsYVz66Qoru
@localden localden marked this pull request as ready for review July 10, 2026 21:09
@localden localden requested review from a team as code owners July 10, 2026 21:09
@localden

Copy link
Copy Markdown
Contributor

/lgtm

Easy enough - this fixes 404s.

@mcp-commander mcp-commander Bot added the accepted SEP accepted by core maintainers, but still requires final wording and reference implementation. label Jul 10, 2026

@mcp-commander mcp-commander Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved on behalf of @localden via /lgtm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

accepted SEP accepted by core maintainers, but still requires final wording and reference implementation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants