Skip to content

fix(deps): pin mcp to v1 — v2 renamed FastMCP and breaks the import - #64

Open
tikankika wants to merge 1 commit into
mainfrom
fix/pin-mcp-v1
Open

fix(deps): pin mcp to v1 — v2 renamed FastMCP and breaks the import#64
tikankika wants to merge 1 commit into
mainfrom
fix/pin-mcp-v1

Conversation

@tikankika

Copy link
Copy Markdown
Owner

Vad

mcp>=1.0.0mcp>=1.28.1,<2 i packages/qf-pipeline/pyproject.toml, med uv.lock uppdaterad (mcp 1.25.0 → 1.29.0).

Varför

mcp 2.x döper om FastMCP till MCPServer. Med den gamla golvspecen >=1.0.0 kan en färsk resolve dra in 2.x, och då failar from mcp.server.fastmcp import FastMCP direkt vid import — inte vid något kantfall, utan på första raden.

Övre gränsen är den bärande halvan. Det höjda golvet speglar bara vad låsfilen redan löste ut.

Samma problem finns okorrigerat i ACDM, där testsviten inte ens kollekterar mot en installerad 2.x. Det åtgärdas separat.

Test

uv run --frozen pytest -q i packages/qf-pipeline: 61 passed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KHXjsZxr2d8Mi8WVMqyfEq

mcp 2.x renames FastMCP to MCPServer, so `from mcp.server.fastmcp
import FastMCP` fails outright on a fresh resolve. The old floor
(>=1.0.0) let that happen. Pin to >=1.28.1,<2 and lock mcp 1.29.0.

The upper bound is the load-bearing half; the raised floor just
matches what the lock already resolved.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant