Skip to content

Commit 9efdf2a

Browse files
jeffhandleyCopilot
andauthored
Use "backward-compatible" and "forward-compatible"
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent e5e5b39 commit 9efdf2a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/versioning.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The ModelContextProtocol specification continues to evolve rapidly, and it's imp
99
Given a version number MAJOR.MINOR.PATCH, the package versions will increment the:
1010

1111
* MAJOR version when incompatible API changes are included
12-
* MINOR version when functionality is added in a backward compatible manner
12+
* MINOR version when functionality is added in a backward-compatible manner
1313
* PATCH version when backward-compatible bug fixes are included
1414

1515
*A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements.*
@@ -43,7 +43,7 @@ All releases are posted to https://github.com/modelcontextprotocol/csharp-sdk/re
4343

4444
### Specification schema changes
4545

46-
If the MCP specification changes the schema for JSON payloads, the C# SDK may use the [`McpSession.NegotiatedProtocolVersion`](https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.McpSession.html#ModelContextProtocol_McpSession_NegotiatedProtocolVersion) to dynamically change the payload schema, potentially using internal data transfer objects (DTOs) to achieve the needed deserialization behavior. These techniques will be applied where feasible to maintain backwards- and forwards-compatibility between MCP specification versions.
46+
If the MCP specification changes the schema for JSON payloads, the C# SDK may use the [`McpSession.NegotiatedProtocolVersion`](https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.McpSession.html#ModelContextProtocol_McpSession_NegotiatedProtocolVersion) to dynamically change the payload schema, potentially using internal data transfer objects (DTOs) to achieve the needed deserialization behavior. These techniques will be applied where feasible to maintain backward- and forward-compatibility between MCP specification versions.
4747

4848
Refer to the following prototypes for illustrations of how this could be achieved:
4949

0 commit comments

Comments
 (0)