You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@superset.apache.org by ru...@apache.org on 2026/09/10 00:51:58 UTC
(superset) branch master updated: fix(deps): cap mcp to <2.0 to match fastmcp 3.x's own constraint (#44039)
This is an automated email from the ASF dual-hosted git repository.
rusackas pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/superset.git
The following commit(s) were added to refs/heads/master by this push:
new 4edf7b10052 fix(deps): cap mcp to <2.0 to match fastmcp 3.x's own constraint (#44039)
4edf7b10052 is described below
commit 4edf7b1005282e605a756ed3c249a2a9a412d77b
Author: Evan Rusackas <ev...@preset.io>
AuthorDate: Wed Sep 9 17:51:51 2026 -0700
fix(deps): cap mcp to <2.0 to match fastmcp 3.x's own constraint (#44039)
Co-authored-by: Claude Code <no...@anthropic.com>
---
pyproject.toml | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/pyproject.toml b/pyproject.toml
index 63e19dbf979..dbaa2ef3290 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -198,7 +198,11 @@ excel = ["xlrd>=2.0.2, <2.1"]
excel-export = ["boto3"]
fastmcp = [
"fastmcp>=3.4.7,<4.0",
- "mcp>=1.29.1,<3.0",
+ # fastmcp 3.x itself requires mcp<2.0; the upper bound here was looser
+ # than that until Dependabot proposed mcp 2.1.1 and the resolver caught
+ # the conflict (#43876). Capped to match what fastmcp 3.x actually
+ # supports until this extra moves to fastmcp 4.x, which accepts mcp 2.x.
+ "mcp>=1.29.1,<2.0",
# tiktoken backs the response-size-guard token estimator. Without
# it, the middleware falls back to a coarser character-based
# heuristic that under-counts JSON-heavy MCP responses.