chore(deps): upgrade go-sdk to v1.7.0-pre.1 (new MCP spec)#2787
Draft
SamMorrowDrums wants to merge 3 commits into
Draft
chore(deps): upgrade go-sdk to v1.7.0-pre.1 (new MCP spec)#2787SamMorrowDrums wants to merge 3 commits into
SamMorrowDrums wants to merge 3 commits into
Conversation
Bumps github.com/modelcontextprotocol/go-sdk v1.6.1 -> v1.7.0-pre.1, the pre-release that implements the new stateless MCP spec (SEP-2575 server/discover, SEP-2567 sessionless, MRTR per SEP-2322). The only source-visible change is tool annotation serialization: the new SDK drops `omitempty` on ToolAnnotations.ReadOnlyHint and IdempotentHint, so false values are now emitted explicitly. Regenerated the 113 affected toolsnaps to match. No behavioural changes; build, vet, test and lint all pass. Refs: github/copilot-mcp-core#1709 Co-authored-by: Copilot <[email protected]>
Auto-generated by license-check workflow
Pins both the stdio and streamable-http MCP Server Diff jobs to the 3.0 branch of SamMorrowDrums/mcp-server-diff (commit 3c2d5ea), which normalizes cross-spec-version churn: _meta protocol plumbing, CacheableResult cache hints, the initialize envelope, and tool-annotation default hints. Without it the go-sdk v1.6.1 -> v1.7.0-pre.1 bump would surface ~113 spurious idempotentHint/readOnlyHint:false diffs from the SDK dropping omitempty. Temporary commit pin; move to the v3.0.0 tag once it ships. Refs: github/copilot-mcp-core#1709 Co-authored-by: Copilot <[email protected]>
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.
What
Upgrades
github.com/modelcontextprotocol/go-sdkv1.6.1 → v1.7.0-pre.1, the pre-release that implements the new stateless MCP spec:server/discover(stateless,initializeno longer required)Mcp-Session-Id)Part of the epic github/copilot-mcp-core#1709 (MCP Spec adoption — MRTR & stateless transport).
Changes
go.mod/go.sum: SDK bump + two new indirect deps (golang.org/x/sync,golang.org/x/time) pulled in by the SDK's MRTR/logging code.omitemptyfromToolAnnotations.ReadOnlyHintandIdempotentHint, so their documented default (false) is now emitted explicitly instead of omitted. (The SDK offersMCPGODEBUG=hintomitempty=1to restore the old behaviour; we intentionally adopt the new, explicit serialization.).github/workflows/mcp-diff.yml: pinned both jobs to the cross-spec-awaremcp-server-diff@3c2d5ea(see below).No application code changes were needed — the Go API is backward compatible.
script/test,go vet, andscript/lintare all green;script/generate-docsproduced no changes.Does one binary serve both old and new clients? Yes.
Verified empirically against this build:
supportedProtocolVersionsspans2026-07-28(new, stateless) down to2024-11-05, the server registers both the legacyinitializehandler and the newserver/discoverhandler, and it negotiates per connection. An old client sendinginitializewithprotocolVersion: 2025-06-18negotiates2025-06-18and gets a fulltools/listover both stdio and streamable-http; the new stateless path (server/discover+tools/listwith noinitialize, reserved_metaper request) serves at2026-07-28. So this server stays backward-compatible with existing clients while serving the newest spec — no routing split / legacy fork required at the OSS layer.Diff coverage
.github/workflows/mcp-diff.yml(stdio + streamable-http) diffs this branch's server againstmainacross the config matrix. It is pinned tomcp-server-diff@3c2d5ea, which normalizes cross-spec-version churn —_metaprotocol plumbing, CacheableResult cache hints, theinitializeenvelope, and tool-annotation default hints — so the annotation-serialization change above shows up as no diff rather than ~113 spuriousidempotentHint/readOnlyHint: falseentries. The pin is temporary; it moves to thev3.0.0tag once that ships.Co-authored-by: Copilot [email protected]