Merged
Conversation
Contributor
|
@Copilot Thank you for the contribution! Could you fix the following issue(s)? ⚠ Invalid PR templateThis PR does not appear to have been filed using the MLflow PR template. Please copy the PR template from here and fill it out. |
- Removed mlflow/diviner/ directory - Removed tests/diviner/ directory - Removed examples/diviner/ directory - Removed docs/api_reference/source/python_api/mlflow.diviner.rst file - Updated mlflow/__init__.py to remove diviner lazy loader - Updated mlflow/models/__init__.py to remove diviner from docstring - Updated mlflow/ml-package-versions.yml to remove diviner entry - Updated mlflow/ml_package_versions.py to remove diviner entry - Updated mlflow/telemetry/constant.py to remove diviner from flavors list - Updated mlflow/types/utils.py to remove diviner comment - Updated requirements/extra-ml-requirements.txt to remove diviner requirement - Updated tests/check_mlflow_lazily_imports_ml_packages.py - Updated tests/conftest.py to remove diviner test path - Updated tests/examples/test_examples.py to remove diviner example test - Updated tests/pyfunc/docker/test_docker_flavors.py to remove diviner docker test - Updated docs/api_reference/api_inventory.txt to remove diviner API references Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remove diviner flavor from MLflow codebase
Remove deprecated diviner flavor
Nov 12, 2025
harupy
reviewed
Nov 12, 2025
- Removed diviner flavor section from docs/docs/classic-ml/model/index.mdx - Removed diviner example reference from docs/docs/classic-ml/tutorials-and-examples/index.mdx Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
BenWilson2
approved these changes
Nov 14, 2025
Contributor
BenWilson2
left a comment
There was a problem hiding this comment.
Looks great! さようなら Diviner
jackiehimel
pushed a commit
to jackiehimel/mlflow
that referenced
this pull request
Nov 21, 2025
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: harupy <17039389+harupy@users.noreply.github.com> Signed-off-by: Jackie Himel <jacqueline.himel@vanderbilt.edu>
mprahl
pushed a commit
to opendatahub-io/mlflow
that referenced
this pull request
Nov 21, 2025
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Tian-Sky-Lan
pushed a commit
to Tian-Sky-Lan/mlflow
that referenced
this pull request
Nov 24, 2025
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: harupy <17039389+harupy@users.noreply.github.com> Signed-off-by: Tian Lan <sky.blue266000@gmail.com>
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.
Related Issues/PRs
#xxx
What changes are proposed in this pull request?
Removes the diviner flavor, deprecated in MLflow 3.6.0.
Directories removed:
mlflow/diviner/- Flavor implementation (618 lines)tests/diviner/- Test suiteexamples/diviner/- Example codedocs/api_reference/source/python_api/mlflow.diviner.rst- API docsFiles updated:
mlflow/__init__.py- Remove lazy loadermlflow/models/__init__.py- Remove from docstringmlflow/ml-package-versions.yml- Remove package configmlflow/ml_package_versions.py- Remove version entrymlflow/telemetry/constant.py- Remove from NON_GENAI_MODULESrequirements/extra-ml-requirements.txt- Remove dependencydocs/api_reference/api_inventory.txt- Remove diviner API referencesdocs/docs/classic-ml/model/index.mdx- Remove diviner flavor sectiondocs/docs/classic-ml/tutorials-and-examples/index.mdx- Remove diviner example referenceHow is this PR tested?
Verified MLflow imports successfully without diviner in namespace. Confirmed other flavors (catboost, h2o, prophet, pmdarima) remain functional.
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
Removed the diviner flavor that was deprecated in MLflow 3.6.0. Users should migrate to alternative time series forecasting solutions.
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?
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.