docs(refs): add MCP breaking changes policy#47
Merged
Conversation
Restructure the Breaking Changes Policy: state the commitments and the breaking / non-breaking definitions once, then apply them per surface under REST/HTTP Endpoints and MCP Server & Tools. Scope the MCP policy to data tools (those requiring an API key); they wrap REST endpoints and follow the same rules. Documentation and navigation tools, tool descriptions, and other definition metadata are excluded. Cover tool deprecation, independent removal, and server/transport/auth changes.
lhagenWP
approved these changes
Jun 16, 2026
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
2 participants
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.
Summary
Add an MCP breaking-changes policy alongside the existing REST policy, and
restructure the Breaking Changes section so the commitments and definitions
are stated once, then applied per surface.
Changes
stated once, then applied under
REST / HTTP EndpointsandMCP Server & ToolsREST endpoints and follow the same rules
metadata; cover tool deprecation, independent removal, and server/transport/auth changes