Sync master

[mprahl]

🛠 DevTools 🛠

Install mlflow from this PR

# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/4/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/4/merge#subdirectory=libs/skinny

For Databricks, use the following command:

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/4/merge

Related Issues/PRs

#xxx

What changes are proposed in this pull request?

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests
• Manual tests

Does this PR require documentation update?

• No. You can skip the rest of this section.
• Yes. I've updated:
  • Examples
  • API references
  • Instructions

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/tracking: Tracking Service, tracking client APIs, autologging
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
• area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
• area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
• area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
• area/projects: MLproject format, project running backends
• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages

How 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" section
• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should 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?

• Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
  Bug fixes, doc updates and new features usually go into minor releases.
• Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
  Bug fixes and doc updates usually go into patch releases.

• Yes (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)

[coderabbitai]

Warning

Rate limit exceeded

@mprahl has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 0 minutes and 51 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 64e138e and 5cdb505.

⛔ Files ignored due to path filters (2)

• docs/static/images/traditional-ml-ui.gif is excluded by !**/*.gif
• mlflow/server/js/nohup.out is excluded by !**/*.out

📒 Files selected for processing (43)

• .github/workflows/master.yml (0 hunks)
• .github/workflows/preview-comment.js (2 hunks)
• dev/set_matrix.py (5 hunks)
• docs/api_reference/api_inventory.txt (0 hunks)
• docs/api_reference/source/python_api/mlflow.diviner.rst (0 hunks)
• docs/docs/classic-ml/deep-learning/pytorch/guide/index.mdx (0 hunks)
• docs/docs/classic-ml/deep-learning/pytorch/index.mdx (0 hunks)
• docs/docs/classic-ml/deep-learning/pytorch/quickstart/quickstart-pytorch.ipynb (0 hunks)
• docs/docs/classic-ml/model/index.mdx (0 hunks)
• docs/docs/classic-ml/traditional-ml/index.mdx (2 hunks)
• docs/docs/classic-ml/traditional-ml/prophet/guide/index.mdx (0 hunks)
• docs/docs/classic-ml/traditional-ml/prophet/index.mdx (2 hunks)
• docs/docs/classic-ml/traditional-ml/sparkml/guide/index.mdx (0 hunks)
• docs/docs/classic-ml/traditional-ml/sparkml/index.mdx (1 hunks)
• docs/docs/classic-ml/tutorials-and-examples/index.mdx (0 hunks)
• docs/docs/genai/tracing/integrations/listing/langchain.mdx (6 hunks)
• docs/docs/genai/tracing/integrations/listing/langgraph.mdx (6 hunks)
• docs/docusaurus.config.ts (3 hunks)
• docs/sidebarsClassicML.ts (2 hunks)
• examples/diviner/MLproject (0 hunks)
• examples/diviner/python_env.yaml (0 hunks)
• examples/diviner/train.py (0 hunks)
• mlflow/__init__.py (0 hunks)
• mlflow/diviner/__init__.py (0 hunks)
• mlflow/gateway/providers/bedrock.py (2 hunks)
• mlflow/ml-package-versions.yml (30 hunks)
• mlflow/ml_package_versions.py (1 hunks)
• mlflow/models/__init__.py (0 hunks)
• mlflow/semantic_kernel/tracing_utils.py (1 hunks)
• mlflow/server/js/src/common/constants.tsx (1 hunks)
• mlflow/telemetry/constant.py (0 hunks)
• mlflow/tracking/fluent.py (1 hunks)
• mlflow/types/utils.py (0 hunks)
• requirements/extra-ml-requirements.txt (0 hunks)
• tests/check_mlflow_lazily_imports_ml_packages.py (0 hunks)
• tests/conftest.py (0 hunks)
• tests/crewai/test_crewai_autolog.py (16 hunks)
• tests/diviner/test_diviner_model_export.py (0 hunks)
• tests/examples/test_examples.py (0 hunks)
• tests/gateway/providers/test_bedrock.py (3 hunks)
• tests/pyfunc/docker/test_docker_flavors.py (0 hunks)
• tests/semantic_kernel/test_semantic_kernel_autolog.py (7 hunks)
• tests/tracking/fluent/test_fluent.py (1 hunks)

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}