Skip to content

chore(deps): pin mcp<2.0 — prevent silent breaking upgrade on self-deploy - #748

Open
bradbrok wants to merge 1 commit into
mainfrom
fix/mcp-pin-lt-2
Open

chore(deps): pin mcp<2.0 — prevent silent breaking upgrade on self-deploy#748
bradbrok wants to merge 1 commit into
mainfrom
fix/mcp-pin-lt-2

Conversation

@bradbrok

Copy link
Copy Markdown
Owner

Summary

  • Pins mcp>=1.27,<2.0 in pyproject.toml (was unbounded at >=1.27)

Why

Every update_and_restart() rebuilds dependencies. The day mcp 2.0.0 lands on PyPI a routine 4am self-deploy would pull it in silently. mcp (FastMCP) is load-bearing for the whole fleet — pinky_memory, pinky_messaging, pinky_self, pinky_outreach, pinky_calendar, and the shared SSE gateway on :8890 all build on it. A breaking import = every agent loses tools simultaneously.

Upstream claude-agent-sdk v0.2.96 already guards against this for the same reason (release notes).

Pure pin — zero behaviour change today, prevents a future fleet outage.

Closes #734.

https://claude.ai/code/session_011D61mHWpHKmtzFJmzcQfxx


Generated by Claude Code

Upstream claude-agent-sdk v0.2.96 guards against mcp 2.0 for the same
reason — closes #734.

https://claude.ai/code/session_011D61mHWpHKmtzFJmzcQfxx
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.

Pin mcp<2.0 — unbounded mcp>=1.27 can pull a breaking 2.0 into every MCP server on a routine deploy

2 participants