Related Issues/PRs

What changes are proposed in this pull request?

Removes the promptflow flavor completely from the MLflow codebase following its deprecation in 3.6.0.

Deleted:

• mlflow/promptflow/ - flavor implementation (502 lines)
• tests/promptflow/ - test suite (134 lines)
• examples/promptflow/ - example flows (240 lines)
• Documentation files and API references

Updated:

• mlflow/__init__.py - removed LazyLoader and exports
• mlflow/ml-package-versions.yml - removed package configuration
• mlflow/ml_package_versions.py - removed from package info dict
• mlflow/telemetry/constant.py - removed from GENAI_MODULES
• requirements/extra-ml-requirements.txt - removed dependency
• tests/conftest.py - removed from skip list
• docs/api_reference/api_inventory.txt - removed 5 API entries
• docs/src/api_modules.json - removed module reference

Total: 24 files changed, 971 deletions

How is this PR tested?

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

Verified MLflow imports successfully and mlflow.promptflow is not accessible.

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.

The deprecated promptflow flavor has been removed. Users should migrate to alternative solutions as the flavor is no longer available.

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 (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.