Track MCP 2026-07-28 RC integration#281
Draft
leehack wants to merge 85 commits into
Draft
Conversation
Accept and preserve JSON Schema 2020-12 boolean subschemas in MCP tool schemas, including correct true/false validation semantics and regression coverage.
…as-dev-port Preserve JSON Schema boolean subschemas on dev
Sync main into dev 2026 RC
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #281 +/- ##
==========================================
+ Coverage 81.21% 84.92% +3.71%
==========================================
Files 67 70 +3
Lines 10107 15432 +5325
==========================================
+ Hits 8208 13106 +4898
- Misses 1899 2326 +427
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Update conformance alpha3 draft target
Update conformance alpha4 baseline
Add TS 2026 RC interop smoke
* Expand TS 2026 RC interop coverage * Expand 2026 RC interop critical paths * Tighten 2026 RC progress interop assertion
* Update conformance alpha5 and TS RC interop * Tighten TS 2026 RC interop fixture * Clarify 2026-07-28 RC fixture names
Merge current main into dev/2026-07-28-rc to inherit the stable web/WASM export workaround and resolve PR #281 conflicts.
Update MCP conformance alpha7 references and expected failure baselines.
fix: return subscription listen close metadata
chore: clean up example analysis and 2026 previews
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
Tracking PR for the
dev/2026-07-28-rcbranch intomain. This is intentionally a draft integration lane for MCP 2026-07-28 draft/RC work and should not be merged until the RC branch is ready for final stabilization.Current Scope
Tracking Notes
mainalready contains the stable2.2.1JSON Schema boolean subschema fix; the next dev-branch task is to carry that fix intodev/2026-07-28-rcso this tracking PR does not regress it.@modelcontextprotocol/conformance@0.2.0-alpha.2, with the known 2026 RC client fixture gap tracked as an expected failure.Validation
Validation is performed on topic PRs before they merge into
dev/2026-07-28-rc. This tracking PR should be treated as an aggregate integration view, not a final release approval.