Migrating to MLflow v2.21.0
Version v2.21.0 introduces 2 breaking changes. This guide details how to update your code.
Released: 3/14/2025
2
Breaking Changes
6
Migration Steps
13
Affected Symbols
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
mlflow.log_tracemlflow.doctormlflow.tracking.ExperimentViewRunsControlsActionsSelectTagsmlflow.models.ChatAgentmlflow.models.UserAuthPolicymlflow.models.ChatModelmlflow.models.ChatCompletionResponsemlflow.models.LangGraphmlflow.models.LangChainmlflow.serving.fastapimlflow.prompt_registrymlflow.tracingmlflow.trackingBreaking Changes
●Issue #1
Inference server migrated from Flask to FastAPI, breaking custom Flask‑based integrations. Update your client code to use the new FastAPI ASGI endpoints.
●Issue #2
LangGraph integration had a breaking change; the library now expects updated API signatures. Adjust your LangGraph usage accordingly.
Migration Steps
- 1Switch any custom inference server code from Flask routes to FastAPI routes as described in the new inference server documentation.
- 2If you use LangGraph, update your code to match the new API signatures introduced in this release.
- 3Upgrade to MLflow 2.21.0 and verify that mlflow.doctor fallback works automatically; no code change required.
- 4Refresh imports for txtai integration if you previously imported it directly.
- 5Review usage of ExperimentViewRunsControlsActionsSelectTags to ensure proper loading‑state handling after tag operations.
- 6Avoid using tag values that contain ": " without escaping, or update your code to handle the new truncation‑prevention logic.
Release Summary
MLflow 2.21.0 introduces a redesigned documentation site, a Prompt Registry, FastAPI‑based inference server, enhanced tracing, and numerous new integrations and bug fixes.
Need More Details?
View the full release notes and all changes for MLflow v2.21.0.
View Full Changelog