Spaces:
Running
Running
Jeremiah Lowin Copilot commited on
Update docs/getting-started/installation.mdx
Browse filesCo-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
docs/getting-started/installation.mdx
CHANGED
|
@@ -65,7 +65,7 @@ Prior to `fastmcp==2.3.0` and `mcp==1.8.0`, the 2.x API always mirrored the 1.0
|
|
| 65 |
While we make every effort not to introduce backwards incompatible changes to our public APIs and behavior, FastMCP exists in a rapidly evolving MCP landscape. We're committed to bringing the most cutting-edge features to our users, which occasionally necessitates changes to existing functionality.
|
| 66 |
|
| 67 |
As a practice, breaking changes will only occur on minor version changes (e.g., 2.3.x to 2.4.0). A minor version change indicates either:
|
| 68 |
-
- A new feature set
|
| 69 |
- An implementation of breaking changes that could affect behavior if users upgrade blindly
|
| 70 |
|
| 71 |
For users concerned about stability in production environments, we recommend pinning FastMCP to a specific version in your dependencies.
|
|
|
|
| 65 |
While we make every effort not to introduce backwards incompatible changes to our public APIs and behavior, FastMCP exists in a rapidly evolving MCP landscape. We're committed to bringing the most cutting-edge features to our users, which occasionally necessitates changes to existing functionality.
|
| 66 |
|
| 67 |
As a practice, breaking changes will only occur on minor version changes (e.g., 2.3.x to 2.4.0). A minor version change indicates either:
|
| 68 |
+
- A significant new feature set that warrants a new minor version
|
| 69 |
- An implementation of breaking changes that could affect behavior if users upgrade blindly
|
| 70 |
|
| 71 |
For users concerned about stability in production environments, we recommend pinning FastMCP to a specific version in your dependencies.
|