Repository navigation
chore(mcp): update MCP packages to 2.3.1 and conformance to alpha.12 - #2574
Merged
Merged
Conversation
… to alpha.12 - legacy-compat handler rejects a factory instance still serving another request before taking ownership, so the error path can't close it - McpAgent: DELETE ends the session immediately (404 for its ID) while teardown stays deferred to the alarm - conformance: referee alpha.12, driver covers json-schema-2020-12-preservation, fixture ported from @modelcontextprotocol/server@2.3.1, stale baseline removed
🦋 Changeset detectedLatest commit: 64e2c53 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
🟡 agents import sizes: 2 entry points grew
Changed exports (17)
How this worksEach runtime export is bundled on its own, minified, and gzipped. Changes smaller than 100 B, or smaller than 1% and 1 KiB, are ignored. Growth over 10% or 5 KiB is marked 🔴. This report is informational and does not fail CI. The workflow artifact contains every measurement. Compared |
agents
@cloudflare/ai-chat
@cloudflare/codemode
hono-agents
@cloudflare/shell
@cloudflare/think
@cloudflare/voice
@cloudflare/worker-bundler
commit: |
Merged
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.
Updates
@modelcontextprotocol/clientand@modelcontextprotocol/serverto 2.3.1,@modelcontextprotocol/sdkto 1.32.1, and the conformance referee to0.2.0-alpha.12. It also fixes two server bugs that the new SDK and referee exposed.Server.connect()rejects an instance that's already connected. When acreateMcpHandlerfactory returned one shared instance, the second Legacy request failed and its teardown then closed that instance, cutting off the request still using it.createLegacyCompatibilityRequestHandlernow rejects a still-serving instance before taking ownership of it, the same check upstream added on the modern path.McpAgentsession termination:alpha.12'sserver-session-lifecyclescenario found thatDELETEreturned 204 but the session kept being served until the deferred teardown alarm ran. The spec requires 404 for a terminated session ID._cf_terminateSession()schedules the teardown and then clears the stored initialize request, so every route treats the ID as unknown straight away.json-schema-2020-12-preservationclient scenario. The vendored fixture is ported from@modelcontextprotocol/server@2.3.1, adding the scope-challenge registrations.http-standard-headersleaves the 2026-07-28 client baseline becausealpha.12fixed the referee bug behind it.Tests ran: the full
agentsandcodemodesuites, everypnpm run test:conformancelane, and a typecheck of every MCP-consuming project. Both fixes have regression tests that fail without them.