Document standing support for new MCP revisions - #1826
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Documents the SDK’s commitment to timely support for future MCP revisions.
Changes:
- Commits to supporting each new revision alongside publication.
- Clarifies ongoing SEP tracking through revision project boards.
Show a summary per file
| File | Description |
|---|---|
docs/roadmap.md |
Adds the standing revision-support plan. |
Review details
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
jeffhandley
approved these changes
Aug 19, 2026
jeffhandley
left a comment
jeffhandley
left a comment
Contributor
There was a problem hiding this comment.
Looks great. We also need to backport this to the release/1.x branch so that the 1.x version of this document captures the same statement.
Once we merge both main and release/1.x, we can trigger a docs publish workflow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tier 1 requires a forward-looking commitment to support new protocol features. This update makes the C# SDK's standing plan explicit: support each new MCP specification revision alongside the specification, following the precedent set by the 2026-07-28 revision.
It also clarifies that accepted SEPs are tracked on each revision's project board throughout development so implementation is ready when the revision is published, while preserving the existing protocol repository context.