Update MCP sdk to latest 1.29 - #29459
Merged
Merged
Conversation
Contributor
Author
|
This change is part of the following stack: Change managed by git-spice. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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.
Description
Update MCP from 1.27.0 to 1.29.0, which includes the fix for the
tscpath: modelcontextprotocol/typescript-sdk#1623 — this is the motivation for the upgrade.1.29.0 is the latest 1.x (anything newer is the
2.0.0-betaprerelease line, which we deliberately avoid). Bumped in all workspaces that depend on it (front,sdks/js,cli/dust-cli,extension) plus the rootoverridespin, and regeneratedpackage-lock.json.Why this is safe
Every change between 1.27.0 and 1.29.0 is a bug fix or v1.x backport — no intentional breaking API changes:
scopes_supportedfrom resource metadata by default; default toclient_secret_basicwhen the server omitstoken_endpoint_auth_methods_supported; reject plain JSON Schema objects passed asinputSchema(Claude has a max_token issue #1596); timeout/abort cleanup fixes; RFC 8252 loopback port relaxation.sizefield toResourceSchema; add typings exports / missingpackage.jsontypes (thetscpath fix above, feat(assistant builder): add basic avatar picker #1623); allow advertising extensions in the capability object; always setwindowsHideon Windows for stdio.The only behavior-narrowing change, #1596 (
tool()/registerTool()now throw if passed a plain JSON Schema instead of a Zod shape), does not affect us: everyregisterToolcall site passes a ZodZodRawShape(register.ts,mcp_internal_actions/wrappers.ts,extension/shared/tools/index.ts). The plain{ type: "object", ... }objects in the codebase are our own config types / mock wire-formatToolobjects, never arguments toregisterTool.The auth-default changes are also no-ops for us:
remote_mcp_servers_resource.tsalready branches explicitly onclient_secret_post/client_secret_basicand already prioritizes resource-metadatascopes_supported. NoStdioClientTransportusage, so the Windows stdio change is irrelevant.Tests
npx tsgo --noEmitinfront(type-check). No source changes required — dependency bump only.Risk
Low. Patch/minor bug-fix bump with no breaking API changes affecting our usage. Can be rolled back by reverting the version bump.
Deploy Plan
deploy front