Pin fastmcp to >=2.10.6,<3.0.0 - #9
Open
dmarshall-rgb wants to merge 1 commit into
Open
Conversation
During local debugging, fastmcp 3.0+ was found to break the server (specific symptom not fully documented at the time). >=2.10.6 was confirmed as a working floor; the environment this was tested and is currently running in uses fastmcp 2.14.7. The lower bound reflects a known-good version encountered during testing rather than an exhaustively verified minimum -- lower 2.10.x versions may also work but were not specifically tested. Added the <3.0.0 upper bound to prevent an unintentional upgrade into the breaking 3.0+ line via a loose >= constraint.
Contributor
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
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.
During local debugging, fastmcp 3.0+ was found to break the server (specific symptom not fully documented at the time). >=2.10.6 was confirmed as a working floor; the environment this was tested and is currently running in uses fastmcp 2.14.7. The lower bound reflects a known-good version encountered during testing rather than an exhaustively verified minimum -- lower 2.10.x versions may also work but were not specifically tested.
Added the <3.0.0 upper bound to prevent an unintentional upgrade into the breaking 3.0+ line via a loose >= constraint.