Dependencies: Downgrade to fastmcp<2.7 to fix a breaking change#37
Dependencies: Downgrade to fastmcp<2.7 to fix a breaking change#37
fastmcp<2.7 to fix a breaking change#37Conversation
WalkthroughThe dependency constraint for "fastmcp" was updated from "<3" to "<2.7" in the project configuration to avoid a breaking change. The changelog was also updated to document this adjustment. No other code or configuration changes were made. Changes
Suggested reviewers
Poem
✨ Finishing Touches🧪 Generate Unit Tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
CHANGES.md (1)
4-4: Align changelog entry with existing style conventions
Capitalize the package name toFastMCPfor consistency with other entries and adapt formatting to match prior changelog style (plain-text version numbers).Suggested diff:
- - Dependencies: Downgraded to `fastmcp<2.7` to fix a breaking change + - Dependencies: Downgraded to FastMCP <2.7> to fix a breaking change
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
CHANGES.md(1 hunks)pyproject.toml(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: amotl
PR: crate/cratedb-mcp#24
File: pyproject.toml:76-76
Timestamp: 2025-05-17T16:02:09.342Z
Learning: For the cratedb-mcp project, FastMCP pre-2.0 releases provide the same API surface needed by the application, so a lower bound on the FastMCP dependency is not necessary.
CHANGES.md (1)
Learnt from: amotl
PR: crate/cratedb-mcp#24
File: pyproject.toml:76-76
Timestamp: 2025-05-17T16:02:09.342Z
Learning: For the cratedb-mcp project, FastMCP pre-2.0 releases provide the same API surface needed by the application, so a lower bound on the FastMCP dependency is not necessary.
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Python 3.10
🔇 Additional comments (1)
pyproject.toml (1)
77-77: Confirm Upper Bound Adjustment for FastMCP
The dependency constraint has been correctly narrowed from<3to<2.7to avoid the breaking change in newer FastMCP releases. No lower bound is required per project conventions.
What the title says.