5932521552
## Motivation and Context The npm `latest` dist-tag of `@modelcontextprotocol/conformance` points at 0.1.16, the old 0.1 line, while the 2026-07-28 requirement revisions and the frozen-requirements framework live in the 0.2.0 alpha line (`alpha` currently resolves 0.2.0-alpha.11). The runners invoked the bare package name, so `rake conformance` and the conformance CI job resolve whatever `latest` points at: a fresh machine silently downgrades to the old suite while a warm npx cache may keep serving a newer one, and the suite actually in use depends on the environment. Pinning the `alpha` dist-tag puts every run on the line the frozen conformance requirements are anchored to (0.2.0-alpha.10, published 2026-07-27). Running the real alpha suite surfaced the actual client-leg state, so the expected-failures baseline is updated to match: `initialize` now passes (the harness accepts 2026-07-28, fulfilling the TODO on the old entry), and the scenarios pending client-side work are recorded with their reasons: the 2026-07-28 stateless lifecycle and the SEP-2322 MRTR driver, SEP-2243 custom-header mirroring, client-side JSON Schema preservation, the DPoP and WIF authorization extensions, and one `auth/authorization-server-migration` check added to the suite after the alpha.10 anchor. The manual `npx` examples in `conformance/README.md` carry the same pin so local reproduction runs the same suite as the rake task. ## How Has This Been Tested? `npx --yes @modelcontextprotocol/conformance@alpha --version` resolves 0.2.0-alpha.11, and `bundle exec rake conformance` passes the baseline check on both legs: the server leg reports 73 passed with 0 failed and no expected failures, and the client leg fails exactly the scenarios the baseline records. ## Breaking Changes None. The change is confined to the conformance tooling; the shipped gem is untouched.
19 lines
828 B
YAML
19 lines
828 B
YAML
server: []
|
|
client:
|
|
# Pending client-side support for the 2026-07-28 stateless lifecycle: the conformance client
|
|
# still connects through the legacy handshake and has no SEP-2322 MRTR driver yet.
|
|
- request-metadata
|
|
- sep-2322-client-request-state
|
|
# SEP-2243 client-side custom-header mirroring and invalid-tool header gating
|
|
# are not implemented in `MCP::Client::HTTP` yet.
|
|
- http-custom-headers
|
|
- http-invalid-tool-headers
|
|
# Client-side JSON Schema preservation gaps: `$ref` values must reach the caller unresolved.
|
|
- json-schema-ref-no-deref
|
|
- json-schema-2020-12-preservation
|
|
# Unimplemented authorization extensions.
|
|
- auth/dpop
|
|
- auth/dpop-nonce
|
|
- auth/wif-jwt-bearer
|
|
# Fails one check added to the suite after the 0.2.0-alpha.10 requirements anchor.
|
|
- auth/authorization-server-migration
|