-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Upgrade go-sdk to v1.7.0 #2968
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade go-sdk to v1.7.0 #2968
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -89,6 +89,18 @@ func NewMCPServer(ctx context.Context, cfg *MCPServerConfig, deps ToolDependenci | |
| Instructions: inv.Instructions(), | ||
| Logger: cfg.Logger, | ||
| CompletionHandler: CompletionsHandler(deps.GetClient), | ||
| // Advertise tools, prompts, and resources without list-changed | ||
| // notifications. The server has a static set of tools/prompts/resources | ||
| // and never mutates them at runtime, so it never emits list_changed | ||
| // notifications. Left unset, the SDK would infer listChanged:true from | ||
| // the presence of items and advertise a capability we don't support - | ||
| // which the 2026-07-28 spec (subscriptions/listen) makes stricter still. | ||
| // Explicitly declaring these keeps the advertised capabilities honest. | ||
| Capabilities: &mcp.ServerCapabilities{ | ||
| Tools: &mcp.ToolCapabilities{}, | ||
| Prompts: &mcp.PromptCapabilities{}, | ||
| Resources: &mcp.ResourceCapabilities{}, | ||
| }, | ||
|
Comment on lines
+99
to
+103
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done — added |
||
| } | ||
|
|
||
| // Apply any additional server options | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — you're right,
v1.7.0is not identical topre.3. There are 4 intervening commits (827f90b..bc72835):Mcp-Protocol-Versionheader from the outgoing message (streamable HTTP client)writeEvent(SSE perf)I've assessed them: all are transport-layer bug fixes / a micro-optimization, none breaking, and none require changes on our side (they only touch the streamable HTTP client and SSE writing). Updated the PR description to list them and drop the "tag-only release" framing.