chore: pin mcp>=1.28.1,<2 ahead of MCP Python SDK v2 stable release#5840
Open
Altamimi-Dev wants to merge 1 commit into
Open
chore: pin mcp>=1.28.1,<2 ahead of MCP Python SDK v2 stable release#5840Altamimi-Dev wants to merge 1 commit into
Altamimi-Dev wants to merge 1 commit into
Conversation
The MCP Python SDK v2 stable release (targeted 2026-07-27/28) is a major rework with pervasive breaking changes (FastMCP rename, mcp.types split, WebSocket transport removal). Upstream guidance is to add a <2 upper bound before the release. Bound every first-party manifest and regenerate uv.lock; resolution stays on the 1.28.x line. fastmcp needs no change: its own mcp dependency is intersected with our direct <2 pin. Closes IBM#5839 Signed-off-by: Ahmad Al Tamimi <altamimi.dev@gmail.com>
Altamimi-Dev
requested review from
Lang-Akshay,
brian-hussey,
crivetimihai,
ja8zyjits and
msureshkumar88
as code owners
July 24, 2026 17:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
🔗 Related Issue
Closes #5839
📝 Summary
Adds a protective
<2upper bound to themcpdependency across all first-party manifests ahead of the MCP Python SDK v2 stable release (targeted 2026-07-27/28), which is a major rework with pervasive breaking changes (FastMCP→MCPServer rename,mcp.typessplit-out, WebSocket transport removal). Every shipped manifest is bounded tomcp>=1.28.1,<2anduv.lockis regenerated; resolution is unchanged and stays on the 1.28.x line.fastmcpneeds no change — its ownmcpdependency is intersected with our direct<2pin, so our bound constrains the whole resolution.The cookiecutter template (
mcp-servers/templates/python/...) was also bounded (mcp>=1.0.0,<2) for consistency, keeping its lower floor. The v2 migration itself is explicitly out of scope per the issue — this is a purely protective packaging change.📏 Reviewability
triage🏷️ Type of Change
🧪 Verification
grep -rEn 'mcp(>=|==|~=|>)[0-9]' --include='*.toml' --include='*.txt' ...,<2uv lockgrep -c 'specifier = ">=1.28.1,<2"' uv.lockgrep -A1 '^name = "mcp"$' uv.lock | grep versionversion = "1.28.1"uv sync --extra plugins && uv run python -c "import mcp, mcp.types; ..."mcp 1.28.1 OKmake testOnly the resolved-graph metadata changed (mcp specifier); resolved package versions are identical, so the change is runtime-neutral today. Container build is covered by CI — the resolved graph is unchanged so the build cannot differ.
✅ Checklist
make black isort pre-commit)📓 Notes
uv.lockalso shows deterministic byproduct churn from the repo's ownexclude-newer-span = "P10D"config re-resolving on lock (an absoluteexclude-newertimestamp and a couple of transitive marker refinements). No resolved package version changed.