Skip to content

test(conformance): bump referee to 0.2.0-alpha.7; drop server-sse-polling from baseline (conformance#366) #2366

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
felixweinberger merged 1 commit into from
Jun 25, 2026
+8 −13
Merged

test(conformance): bump referee to 0.2.0-alpha.7; drop server-sse-polling from baseline (conformance#366) #2366

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
10 changes: 5 additions & 5 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

9 changes: 2 additions & 7 deletions test/conformance/expected-failures.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
# CI exits 0 if only these fail, exits 1 on unexpected failures or stale entries.
#
# Baseline established against the published @modelcontextprotocol/conformance
# release pinned in package.json (0.2.0-alpha.6). Newer conformance releases
# release pinned in package.json (0.2.0-alpha.7). Newer conformance releases
# are adopted by deliberately bumping the package.json pin and reconciling
# this file in the same change.
#
Expand All @@ -24,7 +24,7 @@ client: []

server:
# --- SEP-2663 (io.modelcontextprotocol/tasks) — server SDK does not implement the tasks extension ---
# Extension-tagged scenarios; selected only by `--suite all` (the alpha.6 referee
# Extension-tagged scenarios; selected only by `--suite all` (the alpha.7 referee
# has no server-side `--suite extensions`). The active/draft/2026 legs never select
# them, so they cannot flag these entries as stale. `tasks-status-notifications` is
# intentionally absent: the referee SKIPs it unconditionally (harness rewrite pending
Expand All @@ -39,8 +39,3 @@ server:
- tasks-dispatch-and-envelope
- tasks-required-task-error
- tasks-mrtr-composition
# --- conformance#256 server-sse-polling — referee-side pending scenario ---
# SHOULD-level checks emit WARNING (priming event + retry field) which the baseline
# checker treats as failure. Selected only by `--suite all`; on hold pending
# conformance#366 (referee sends 2025-03-26 while testing a 2025-11-25 feature; SDK correctly version-gates priming).
- server-sse-polling
2 changes: 1 addition & 1 deletion test/conformance/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@
"test:conformance:all": "pnpm run test:conformance:client:all && pnpm run test:conformance:server:all"
},
"devDependencies": {
"@modelcontextprotocol/conformance": "0.2.0-alpha.6",
"@modelcontextprotocol/conformance": "0.2.0-alpha.7",
"@modelcontextprotocol/client": "workspace:^",
"@modelcontextprotocol/server": "workspace:^",
"@modelcontextprotocol/core": "workspace:^",
Expand Down
Loading