chore: bump ext-apps + example servers to 1.7.1, sdk to 1.29.0#44
Open
chore: bump ext-apps + example servers to 1.7.1, sdk to 1.29.0#44
Conversation
ext-apps@1.7.x peers on @modelcontextprotocol/sdk ^1.29.0, which required bumping the pinned sdk from 1.24.2 and adapting to its StreamableHTTPServerTransport refactor: - redisTransport: sessionId is now a readonly getter on the Node wrapper; inject it (and _initialized) on the underlying web-standard transport so resumed sessions validate. Also guard message.id which is now optional on JSONRPCMessage. - shttp.integration.test: handleRequest now routes through @hono/node-server, so the mock IncomingMessage needs url/host/ rawHeaders/on/off/resume, and the session-id header now arrives via writeHead instead of setHeader.
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
Updates the mounted MCP App example servers and
@modelcontextprotocol/ext-appsto 1.7.1 (release notes).ext-apps@1.7.x peers on
@modelcontextprotocol/sdk ^1.29.0, so this also bumps the pinned sdk from1.24.2→1.29.0and adapts to itsStreamableHTTPServerTransportrefactor (now wraps a web-standard transport via@hono/node-server).Code changes
redisTransport.ts—sessionIdis now a readonly getter on the Node wrapper; inject it (and_initialized) on the underlying web-standard transport so resumed sessions passvalidateSession. Also guardmessage.id, which is now optional onJSONRPCMessage.shttp.integration.test.ts—handleRequestnow routes through@hono/node-server, so the mockIncomingMessageneedsurl/host/rawHeaders/on/off/resume, and themcp-session-idresponse header now arrives viawriteHeadinstead ofsetHeader.Note
The
redisTransportresume path reaches into the private_webStandardTransportfield to setsessionIdand_initialized. SDK 1.29 doesn't expose a public way to attach a pre-known session ID to a fresh transport (the previous approach of assigningtransport.sessionIddirectly no longer compiles since it's now a getter). The underlyingWebStandardStreamableHTTPServerTransport.sessionIdis a public writable field — only the path to reach it is private. Worth raising upstream for a supported API; tracked as a follow-up.Test Plan
npm run build✅npm run lint✅npm run typecheck✅npm test— 79/79 ✅node dist/index.jslocally:POST /pdf/mcpandPOST /debug/mcpboth return validinitializeresponses