Add cross-version interop test against the published ext-apps 1.7.5 - #770
Merged
Conversation
Install @modelcontextprotocol/ext-apps@1.7.5 under the npm alias ext-apps-v1 (plus @modelcontextprotocol/sdk@1.30.0, its peer) as devDependencies and run the 2.x App against the 1.x AppBridge and vice versa over an in-memory duplex, with each bridge fronting a real Client+McpServer of its own SDK generation. Covers initialize, notifications, view-to-host requests, tool/resource proxying, error codes, AbortSignal cancellation, teardown and close.
ochafik
force-pushed
the
interop-unit
branch
from
September 8, 2026 14:32
160a780 to
5f6346e
Compare
Contributor
PreviewPreview deployments for this PR have been cleaned up. |
@modelcontextprotocol/ext-apps
@modelcontextprotocol/server-basic-preact
@modelcontextprotocol/server-basic-react
@modelcontextprotocol/server-basic-solid
@modelcontextprotocol/server-basic-svelte
@modelcontextprotocol/server-basic-vanillajs
@modelcontextprotocol/server-basic-vue
@modelcontextprotocol/server-budget-allocator
@modelcontextprotocol/server-cohort-heatmap
@modelcontextprotocol/server-customer-segmentation
@modelcontextprotocol/server-debug
@modelcontextprotocol/server-lazy-auth
@modelcontextprotocol/server-map
@modelcontextprotocol/server-pdf
@modelcontextprotocol/server-scenario-modeler
@modelcontextprotocol/server-shadertoy
@modelcontextprotocol/server-sheet-music
@modelcontextprotocol/server-system-monitor
@modelcontextprotocol/server-threejs
@modelcontextprotocol/server-transcript
@modelcontextprotocol/server-video-resource
@modelcontextprotocol/server-wiki-explorer
commit: |
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.
Adds a unit test that runs the published ext-apps 1.7.5 against this build over an in-memory transport, in both pairings: 2.x
Appwith the 1.xAppBridge(outer client on sdk 1.30), and 1.xAppwith the 2.xAppBridge(outer client on SDK 2.0). It complementssrc/wire-compat.test.ts, which replays hand-shaped 1.x JSON: that file pins message shapes, this one runs the real 1.x code.Why it earns its place: mutation-testing showed a coordinated wire rename in 2.x (sender and shared schema literal changed together, e.g.
ui/notifications/tool-cancelled,ui/open-link'surlparam, orui/initialize'sappInfo) is invisible to the whole same-version suite and towire-compat.test.ts, and is caught only here. It also carries an exact assertion on the rawui/initializeresult the 1.x View receives, so additive drift fails too.Mechanics: two devDependencies (
ext-apps-v1as an npm alias of@modelcontextprotocol/ext-apps@1.7.5, and@modelcontextprotocol/sdk@1.30.0, whose name does not collide with the 2.x split packages; a second alias for the sdk would install it twice and break itsinstanceof McpErrorchecks), and one test file. A provenance test asserts the alias resolves to 1.7.5 and that the 1.x classes descend from sdk-1'sProtocolwhile the 2.x ones do not, so the pairing cannot silently collapse to same-version. 15 tests, 57 assertions.Checked:
npm auditunchanged versus main; lockfile entries allregistry.npmjs.org;check-versions,check-dependency-isolation,npm packcontents, prettier andtsc --noEmitunaffected; the test step runs offline in the CI image (--network none) afternpm ci. 10 of 10 native runs green. The cases in each pairing share one connected fixture and run in file order, noted in a comment.The 1.7.5 pin is deliberate: it is the last 1.x, and
bump-version.mjsleaves it alone. A deliberate 2.x wire change would need a pairings-table decision here, which is the point.