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

ci(conformance): bump harness to 0.2.0-alpha.5 preview (#2927)

Browse source
This commit is contained in:
Max 2026-06-20 16:54:50 +01:00 • committed by GitHub
commit f5fe42f5a4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 43 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

8
.github/actions/conformance/expected-failures.2026-07-28.yml vendored
View file

@ -10,10 +10,10 @@
# 2026 leg reads the `server:` section. Both burn down independently of the
# 2025 legs.
#
# Baseline established against @modelcontextprotocol/conformance pinned in
# .github/workflows/conformance.yml (CONFORMANCE_VERSION = 0.2.0-alpha.4).
# New conformance releases are adopted by deliberately bumping that pin and
# reconciling both this file and expected-failures.yml in the same change.
# Baseline established against the harness pinned via CONFORMANCE_PKG in
# .github/workflows/conformance.yml. New conformance releases are adopted by
# deliberately bumping that pin and reconciling both this file and
# expected-failures.yml in the same change.
#
# Entries are grouped by what unblocks them. As each gap closes the
# corresponding scenarios start passing and MUST be removed from this list

12
.github/actions/conformance/expected-failures.yml vendored
View file

@ -1,11 +1,10 @@
# Conformance scenarios not yet passing against the Python SDK on main.
# CI exits 0 if only these fail, exits 1 on unexpected failures or stale entries.
#
# Baseline established against @modelcontextprotocol/conformance pinned in
# .github/workflows/conformance.yml (CONFORMANCE_VERSION = 0.2.0-alpha.4).
# New conformance releases are adopted by deliberately bumping that pin and
# reconciling both this file and expected-failures.2026-07-28.yml in the same
# change.
# Baseline established against the harness pinned via CONFORMANCE_PKG in
# .github/workflows/conformance.yml. New conformance releases are adopted by
# deliberately bumping that pin and reconciling both this file and
# expected-failures.2026-07-28.yml in the same change.
#
# Entries are grouped by SEP. As each SEP lands in the SDK the corresponding
# scenarios start passing and MUST be removed from this list (the runner fails
@ -41,9 +40,6 @@ client:
- auth/iss-normalized
# --- Pre-existing scenarios that fail on checks added after conformance 0.1.15 ---
# SEP-2350 (scope step-up): WARNING-only; the expected-failures evaluator
# counts WARNINGs as failures.
- auth/scope-step-up
# SEP-990 (enterprise-managed authorization extension): no fixture handler /
# client support for the token-exchange + JWT bearer flow.
- auth/enterprise-managed-authorization

2
.github/actions/conformance/run-server.sh vendored
View file

@ -47,5 +47,5 @@ done
echo "Server ready at $SERVER_URL"
npx --yes @modelcontextprotocol/conformance@"${CONFORMANCE_VERSION:?set CONFORMANCE_VERSION (pinned in .github/workflows/conformance.yml)}" \
npx --yes "${CONFORMANCE_PKG:?set CONFORMANCE_PKG (pinned in .github/workflows/conformance.yml)}" \
server --url "$SERVER_URL" "$@"