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

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

Related Issues/PRs

Resolve #19516

What changes are proposed in this pull request?

This PR adds markdown rendering support to the Compare mode in the Prompt Registry UI, addressing the feature request in #19516.

What changes are proposed in this pull request?

1. Markdown rendering toggle in Compare view (PromptContentCompare.tsx)

   • Added a segmented control toggle (Text/Markdown) in the compare view header
   • When "Markdown" mode is selected, prompts are rendered with proper formatting using GenAIMarkdownRenderer
   • When "Text" mode is selected, prompts are displayed as plain text with diff highlighting (additions in green, deletions in red with strikethrough)
   • Default mode is Markdown (consistent with the Preview mode behavior)

2. Improved Compare mode version selection (usePromptDetailsPageViewState.tsx)

   • Fixed the default version selection when entering Compare mode
   • Previously: Always compared the two latest versions regardless of which version was being previewed
   • Now: When switching from Preview to Compare mode, the currently previewed version is preserved as the baseline (left side), and it's compared against the latest version (or second-to-last if the previewed version is already the latest)

Technical Details:

• Added imports for MarkdownIcon, SegmentedControlButton, SegmentedControlGroup from design system
• Added GenAIMarkdownRenderer from @databricks/web-shared/genai-markdown-renderer
• Added shouldRenderMarkdown state with useState hook
• Conditional rendering based on toggle state

How is this PR tested?

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

Manual Testing:

1. Created prompts with markdown content (headers, lists, bold text, code blocks)
2. Tested Preview mode - markdown renders correctly with existing toggle
3. Tested Compare mode:
   • Toggle switches between Text (with diff highlighting) and Markdown (formatted) views
   • Default is Markdown mode
4. Tested version selection fix:
   • Preview version 1 → Click Compare → Left side shows version 1
   • Preview latest version → Click Compare → Left side shows latest, right side shows second-to-last

Before:

After:

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.
  Added markdown rendering support to the Prompt Registry Compare view, allowing users to toggle between formatted markdown and plain text (with diff highlighting) when comparing prompt versions. Also improved the default version selection in Compare mode to preserve the currently previewed version.

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.

• 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)