Repository navigation
docs(mcp): the minimum mcp is 1.22 (forge-cli #710) - #148
Merged
Merged
Conversation
… pydantic 2.14 (forge-cli #710)
This branch was successfully deployed
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.
Summary
Follows forge-cli #710, which raises the minimum
mcpfrom 1.20 to 1.22 (unreleased).mcp 1.20 and 1.21 import
eval_type_backportfrom pydantic's private_typing_extramodule, and pydantic 2.14 removed it, somcp.server.fastmcpfails to import with pydantic 2.14. Tested in throwaway environments: mcp 1.20 imports with pydantic 2.13.5 and fails with 2.14.0, and 1.22 is the first 1.x release that imports with 2.14.0.docs/cli/mcp.md: the dependency pin row showsmcp>=1.22,<3.0, marked unreleased, with the 0.19.0 pin noted. The "pinmcp>=1.20,<2.0yourself" advice now says 1.22 and explains why 1.20 and 1.21 break.docs/walkthrough/mcp-output-port.md: the same pinning advice, corrected.The 0.15.0 release notes keep
mcp>=1.20, since that is what that release shipped.Merge after forge-cli #710.