Skip to content

chore: update conformance #1114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yarolegovich merged 1 commit into from
Jul 27, 2026
+9 −24
Merged

chore: update conformance #1114

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/conformance.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ permissions:
contents: read

env:
CONFORMANCE_VERSION: "0.2.0-alpha.9"
CONFORMANCE_VERSION: "0.2.0-alpha.10"

jobs:
server-conformance:
Expand Down
31 changes: 8 additions & 23 deletions conformance/baseline.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,29 +1,14 @@
server:
# The `server-stateless` scenario ships with the `@modelcontextprotocol/conformance@0.2.0-alpha.9`
# suite pinned by the workflow, which still enforces the pre-PR-3002
# (https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3002) spec:
# - `clientInfo` in the per-request `_meta` is required (MUST).
# - `serverInfo` is a body field on `DiscoverResult`.
# PR #3002 relaxes `clientInfo` to SHOULD and moves `serverInfo` into every
# response's `_meta`. The Go SDK follows the updated spec, so the following
# checks in the `server-stateless` scenario fail against the pinned suite:
# - sep-2575-request-meta-invalid-missing-client-info
# - sep-2575-http-server-meta-invalid-400
# - sep-2575-server-implements-discover
# Remove this entry when the conformance suite is bumped to a release that
# incorporates PR #3002.
- server-stateless

client:
# OAuth mechanisms not implemented by the Go MCP SDK.
- auth/client-credentials-basic
- auth/client-credentials-jwt
- auth/enterprise-managed-authorization

# Upstream conformance mock inconsistency: the scenario's hand-rolled
# server/discover handler advertises "2026-07-28" but delegates every
# other method to a pinned @modelcontextprotocol/sdk that rejects that
# version at the HTTP layer.
# Remove this entry when the conformance suite is bumped to a release that
# fixes this issue.
- json-schema-ref-no-deref
# SEP-1932 (DPoP Sender-Constrained Tokens) client-side support not yet
# implemented by the Go MCP SDK.
- auth/dpop
- auth/dpop-nonce

# SEP-1933 (Workload Identity Federation JWT-bearer) client-side support
# not yet implemented by the Go MCP SDK.
- auth/wif-jwt-bearer
Loading