Deprecate model logging of OpenAI flavor#19325
Merged
B-Step62 merged 6 commits intomlflow:masterfrom Dec 12, 2025
Merged
Conversation
…project, including guides, tutorials, and autologging support. Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
…uding autologging and RLHF architecture visuals. Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request deprecates the model logging capability of the OpenAI flavor in MLflow, directing users to use the prompt registry instead (mlflow.genai.register_prompt). This change simplifies MLflow's offerings by focusing on the prompt registry for managing OpenAI prompt templates.
Key Changes:
- Added deprecation decorators to
save_model()andlog_model()functions in the OpenAI flavor - Removed comprehensive OpenAI documentation including guides, tutorials, and notebooks
- Removed OpenAI from the sidebar navigation and flavor index page
Reviewed changes
Copilot reviewed 11 out of 15 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| mlflow/openai/model.py | Added @deprecated decorators to save_model() and log_model() functions directing users to mlflow.genai.register_prompt |
| docs/sidebarsGenAI.ts | Removed the entire OpenAI section from the GenAI sidebar navigation (including guide, autologging, and tutorials) |
| docs/docs/genai/flavors/openai/notebooks/openai-quickstart.ipynb | Deleted introductory tutorial notebook for OpenAI flavor |
| docs/docs/genai/flavors/openai/notebooks/openai-embeddings-generation.ipynb | Deleted embeddings tutorial notebook |
| docs/docs/genai/flavors/openai/notebooks/openai-code-helper.ipynb | Deleted code helper tutorial notebook |
| docs/docs/genai/flavors/openai/notebooks/openai-chat-completions.ipynb | Deleted chat completions tutorial notebook |
| docs/docs/genai/flavors/openai/notebooks/index.mdx | Deleted tutorials index page |
| docs/docs/genai/flavors/openai/index.mdx | Deleted main OpenAI flavor landing page |
| docs/docs/genai/flavors/openai/guide/index.mdx | Deleted detailed OpenAI guide documentation |
| docs/docs/genai/flavors/openai/autologging/index.mdx | Deleted autologging documentation |
| docs/docs/genai/flavors/index.mdx | Removed OpenAI reference from the GenAI flavors overview and logo card |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
serena-ruan
reviewed
Dec 11, 2025
serena-ruan
reviewed
Dec 11, 2025
…he new MLflow Prompt Registry. Deprecate the `mlflow.openai.log_model()` API in favor of improved prompt management features. Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
… and update related OpenAI tracing documentation to clarify the tracking capabilities of MLflow. Adjustments made to enhance clarity and focus on the current features. Signed-off-by: Tomu Hirata <tomu.hirata@gmail.com>
Collaborator
Author
|
Tagged with 3.8.0, but not a blocker for RC |
Contributor
|
Documentation preview for 5384721 is available at: Changed Pages (7)
More info
|
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
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.
🛠 DevTools 🛠
Install mlflow from this PR
For Databricks, use the following command:
Related Issues/PRs
n/a
What changes are proposed in this pull request?
The model logging of the OpenAI flavor is essentially for saving the prompt templates. Since we now have prompt registry, we want to deprecate the model logging capability of OpenAI flavor to simplify our offerings.
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.