modelcontextprotocol/rust-sdk
Watch
1
0
Fork
You've already forked rust-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

ci: expose extension conformance gaps (#1019)

Browse source
This commit is contained in:
Dale Seo 2026-07-21 10:23:55 -04:00 • committed by GitHub
commit a8308dc943
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 95 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

6
conformance/expected-failures-2026-07-28.yaml
View file

@ -1,7 +1,11 @@
# Known failures for the pinned 2026-07-28 draft conformance suite
# (@modelcontextprotocol/conformance DRAFT_CONFORMANCE_VERSION).
#
# The full suites run in CI with `--expected-failures` pointing at this file:
# The full versioned-spec suites run in CI with `--expected-failures` pointing
# at this file. Extension scenarios are filtered out by `--spec-version` and
# tracked separately in `expected-failures-extensions.yaml`.
#
# Within the versioned-spec suites:
# - a scenario failing that is NOT listed here fails the build
# - a scenario listed here that starts passing also fails the build (stale entry),
# so remove it from this list when the underlying issue is fixed.

32
conformance/expected-failures-extensions.yaml Normal file
View file

@ -0,0 +1,32 @@
# Known failures for informational extension scenarios in
# @modelcontextprotocol/conformance DRAFT_CONFORMANCE_VERSION.
#
# Extensions are not selected by a `--spec-version` run and do not count toward
# SDK tiering. CI runs them separately so a green versioned-spec suite does not
# hide extension gaps.
#
# This is a strict baseline:
# - an unlisted failure fails the build
# - a listed scenario that starts passing fails the build as a stale entry
#
# When bumping DRAFT_CONFORMANCE_VERSION, review the available extension and
# pending scenarios and update this file deliberately.
server:
# SEP-2663 Tasks Extension, tracked in #868.
# `tasks-status-notifications` is intentionally absent: the upstream check is
# currently skipped, and CI should fail if it becomes active but does not pass.
- tasks-lifecycle
- tasks-capability-negotiation
- tasks-wire-fields
- tasks-request-state-removal
- tasks-mrtr-input
- tasks-request-headers
- tasks-dispatch-and-envelope
- tasks-required-task-error
- tasks-mrtr-composition
client:
# Informational OAuth extension scenarios.
- auth/client-credentials-jwt
- auth/enterprise-managed-authorization