Skip to content

Bump mcp from 2.0.1 to 2.2.0 #56

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
Changyong Gong (chagong) merged 2 commits into from
Oct 19, 2026
Merged

Bump mcp from 2.0.1 to 2.2.0 #56

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5153431
Bump mcp from 2.0.1 to 2.2.0
dependabot[bot] Oct 19, 2026
c2e15f1
Decouple CI dependency checks from documentation
chagong Oct 19, 2026
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 CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,11 +217,11 @@ OIDC/RBAC access, hosted readiness, or wiki publication.

[`requirements-ci.txt`](requirements-ci.txt) pins PyYAML, `packaging`, and PyPA
`build`. [`constraints-ci.txt`](constraints-ci.txt), loaded by the CI
requirements and clean wheel installation, fixes the tested MCP baseline at
`mcp==2.0.1`, within both runtime manifests' supported range. This is not a full
dependency lock or coverage of every newer MCP release. MCP 2.2.0 masks
tool-error details asserted by existing wiki protocol tests; review the
constraint when updating SDK support rather than weakening those assertions.
requirements and clean wheel installation, records the tested MCP baseline.
See that file for the current version, which must satisfy both runtime
manifests' supported ranges. This is not a full dependency lock or coverage of
every newer MCP release. When updating MCP, rerun the protocol tests and
review behavior changes rather than weakening their assertions.
`compileall` checks syntax, not formatting, types, or style.

Actions and actionlint source are pinned to immutable commits. Dependabot
Expand Down
5 changes: 2 additions & 3 deletions constraints-ci.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,2 @@
# Preserve the existing MCP protocol-test baseline without changing runtime ranges.
# Newer SDK error masking needs a separate runtime compatibility change.
mcp==2.0.1
# Pin the MCP version exercised by CI within both runtime manifests' ranges.
mcp==2.2.0
2 changes: 1 addition & 1 deletion requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ azure-keyvault-secrets>=4.9.0
python-dotenv==1.2.2
PyJWT[crypto]>=2.9.0
PyYAML==6.0.3
mcp>=2.0.0,<3
mcp>=2.2.0,<3
dulwich==1.2.14
urllib3>=2.2.2
opentelemetry-api>=1.44.0,<2
Expand Down
1 change: 0 additions & 1 deletion tests/test_ci_workflow.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,6 @@ def test_ci_dependency_baseline_satisfies_both_runtime_manifests(self):
for pin in pins:
version, = [spec.version for spec in pin.specifier if spec.operator == "=="]
self.assertIn(version, runtime[pin.name].specifier)
self.assertIn(str(pin), (ROOT / "CONTRIBUTING.md").read_text(encoding="utf-8"))

def test_both_suites_run_directly_so_failures_fail_the_job(self):
for job_id, command in (
Expand Down