Repository navigation
fix(mcp): support July 2026 while preserving legacy stdio - #1085
Merged
Merged
Conversation
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.
The previous SDK supports legacy initialization but does not implement July 2026 stateless discovery. Upgrade the existing mcp-go dependency from v0.54.1 to v1.3.0 and explicitly choose private, zero-TTL cache hints. Preserve all four legacy revisions and existing text/error semantics; add real-wire proof for the July model without introducing another server or transport.
Follows merged PR1084 and PR1083. GitHub automatically transitioned the base to main after the prerequisite merge. A normal main merge preserves the reviewed history; all 723 MCP/CLI/dependency entries match the prior reviewed source and all 34 incoming plugin files exactly match main. The diff remains the same 11 SDK/protocol/docs/plan files.
Validation:
7943d6cpasses four legacy revisions and stateless2026-07-28: discovery, typed calls/errors, exact synthetic local documentation, explicit complete/private/zero metadata, ordering, version/capability isolation, clean framing and bounded shutdown.7943d6ccandidate → clean40ef2b4/SDK0.54.1 (legacy pass; July discovery-32601) → candidate July/mixed pass. No published history, installed binary or session was reset.8be6554122c60a6738f82e77b2615b5e27b2775fe58a3d1f1cec39fdbcd0a6ad(vcs.modified=false). The six-task/two-PR plan is complete; the final MCP/CLI/dependency trees match the independently reviewed Task5 source. All four hosted cross-plugin and typed-E2E checks passed at the prior reviewed source. Fresh MCP tests, the root standalone plugin integration and the actual five-version CLI wire matrix pass at this integration commit. Full native CI passed at this exact main-based head: race/coverage Go suite, all required checks, lint, build, examples and policy. CodeQL security/quality and the PR OSV scan passed. All four cross-plugin/IaC checks also passed at this head. Independent integration spec and quality reviews pass with no findings.The packaged maintainer smoke client intentionally accepts release-form versions only. An additional probe of this source pseudo-version returned bounded
version_unknownbefore fixture calls; it was not bypassed or relabeled. The verified packaged release pairing remains v0.86.2.These are source-build claims; v0.86.2 predates this change. Text-only results remain. Wire proof does not certify host/directory eligibility, real engine execution, HTTP/authentication, tasks/UI or Compute. General filesystem confinement, resource budgets, rate limits and redaction remain deferred. No installation or deployment is included.
The preexisting Sonic/Go1.27 benchmark-listing diagnostic is explicitly nonblocking under the owner's instruction. No benchmark, workflow-policy or protection override is included; no performance comparison is claimed.