Skip to content

Commit cc4db25

Browse files
authored
chore: update conformance (#1114)
Update to the latest conformance tests version.
1 parent e761950 commit cc4db25

2 files changed

Lines changed: 9 additions & 24 deletions

File tree

.github/workflows/conformance.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ permissions:
1414
contents: read
1515

1616
env:
17-
CONFORMANCE_VERSION: "0.2.0-alpha.9"
17+
CONFORMANCE_VERSION: "0.2.0-alpha.10"
1818

1919
jobs:
2020
server-conformance:

conformance/baseline.yml

Lines changed: 8 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,14 @@
1-
server:
2-
# The `server-stateless` scenario ships with the `@modelcontextprotocol/conformance@0.2.0-alpha.9`
3-
# suite pinned by the workflow, which still enforces the pre-PR-3002
4-
# (https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3002) spec:
5-
# - `clientInfo` in the per-request `_meta` is required (MUST).
6-
# - `serverInfo` is a body field on `DiscoverResult`.
7-
# PR #3002 relaxes `clientInfo` to SHOULD and moves `serverInfo` into every
8-
# response's `_meta`. The Go SDK follows the updated spec, so the following
9-
# checks in the `server-stateless` scenario fail against the pinned suite:
10-
# - sep-2575-request-meta-invalid-missing-client-info
11-
# - sep-2575-http-server-meta-invalid-400
12-
# - sep-2575-server-implements-discover
13-
# Remove this entry when the conformance suite is bumped to a release that
14-
# incorporates PR #3002.
15-
- server-stateless
16-
171
client:
182
# OAuth mechanisms not implemented by the Go MCP SDK.
193
- auth/client-credentials-basic
204
- auth/client-credentials-jwt
215
- auth/enterprise-managed-authorization
226

23-
# Upstream conformance mock inconsistency: the scenario's hand-rolled
24-
# server/discover handler advertises "2026-07-28" but delegates every
25-
# other method to a pinned @modelcontextprotocol/sdk that rejects that
26-
# version at the HTTP layer.
27-
# Remove this entry when the conformance suite is bumped to a release that
28-
# fixes this issue.
29-
- json-schema-ref-no-deref
7+
# SEP-1932 (DPoP Sender-Constrained Tokens) client-side support not yet
8+
# implemented by the Go MCP SDK.
9+
- auth/dpop
10+
- auth/dpop-nonce
11+
12+
# SEP-1933 (Workload Identity Federation JWT-bearer) client-side support
13+
# not yet implemented by the Go MCP SDK.
14+
- auth/wif-jwt-bearer

0 commit comments

Comments
 (0)