Clarify installation for FastMCP 3.0 beta#2953
Conversation
Add pre-release flags to all install commands since 3.0 is in beta. Users must explicitly opt in with --pre (pip) or --prerelease=allow (uv).
WalkthroughThis pull request updates installation documentation for FastMCP 3.0, which is currently in beta and requires explicit prerelease handling. The changes modify installation instructions across multiple package managers (uv add, uv pip install, and pip install) to include appropriate prerelease flags. Additionally, the documentation clarifies optional dependency installation, specifically for the background tasks extra, and adds informational notes about feature requirements in the tasks documentation. Possibly related PRs
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. Comment |
The v3 docs show install commands that would install the stable 2.x release, not the 3.0 beta. Since users reading the 3.0 docs want 3.0, the default instructions should include the pre-release flags.
Changes:
--pre(pip) and--prerelease=allow(uv) to all install commands