Skip to content

Bump mlflow from 2.22.1 to 3.5.0 in /dockerfiles/mlrun-kfp#60

Open
dependabot[bot] wants to merge 1 commit intodevelopmentfrom
dependabot/pip/dockerfiles/mlrun-kfp/mlflow-3.5.0
Open

Bump mlflow from 2.22.1 to 3.5.0 in /dockerfiles/mlrun-kfp#60
dependabot[bot] wants to merge 1 commit intodevelopmentfrom
dependabot/pip/dockerfiles/mlrun-kfp/mlflow-3.5.0

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Feb 2, 2026

User description

Bumps mlflow from 2.22.1 to 3.5.0.

Release notes

Sourced from mlflow's releases.

v3.5.0

MLflow 3.5.0 includes several major features and improvements!

Major Features

  • 🤖 Tracing support for Claude Code SDK: MLflow now provides a tracing integration for both the Claude Code CLI and SDK! Configure the autologging integration to track your prompts, Claude's responses, tool calls, and more. Check out this doc page to get started. (#18022, @​smoorjani)
  • 🎯 Flexible Prompt Optimization API: Introduced a new flexible API for prompt optimization with support for model switching and the GEPA algorithm, enabling more efficient prompt tuning with fewer rollouts. See the documentation to get started. (#18183, #18031, @​TomeHirata)
  • 🎨 Enhanced UI Onboarding: Improved in-product onboarding experience with trace quickstart drawer and updated homepage guidance to help users discover MLflow's latest features. (#18098, #18187, @​B-Step62)
  • 🔐 Security Middleware for Tracking Server: Added a security middleware layer to protect against DNS rebinding, CORS attacks, and other security threats. Read the documentation for configuration details. (#17910, @​BenWilson2)

Features

Bug Fixes

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

PR Type

dependencies, enhancement


Description

  • Upgrade mlflow to 3.5.0

  • Update pinned hashes for lockfile

  • Align extras requirement constraint to 3.5


Diagram Walkthrough

flowchart LR
  extras["extras-requirements.txt mlflow~=3.5"] -- aligns with --> lock["locked-requirements.txt mlflow==3.5.0"]
  lock -- updates --> hashes["Updated sha256 hashes"]
Loading

File Walkthrough

Relevant files
Dependencies
locked-requirements.txt
Lockfile bump to mlflow 3.5.0 with hashes                               

dockerfiles/mlrun-kfp/locked-requirements.txt

  • Bump mlflow from 2.22.1 to 3.5.0
  • Update corresponding sha256 hashes
  • Keep reference comment to extras requirements
+3/-3     
extras-requirements.txt
Raise extras mlflow constraint to 3.5                                       

extras-requirements.txt

  • Update mlflow constraint from ~=2.22 to ~=3.5
  • Maintain other dependency constraints unchanged
+1/-1     

Bumps [mlflow](https://github.com/mlflow/mlflow) from 2.22.1 to 3.5.0.
- [Release notes](https://github.com/mlflow/mlflow/releases)
- [Commits](mlflow/mlflow@v2.22.1...v3.5.0)

---
updated-dependencies:
- dependency-name: mlflow
  dependency-version: 3.5.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Feb 2, 2026
@pull-request-agent
Copy link

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Compatibility

Upgrading to mlflow 3.5 may introduce breaking changes in client/server APIs, tracking store behavior, or plugin interfaces; validate that downstream consumers (e.g., mlrun-kfp components, databricks-sdk integration) remain compatible and that pinned transitive deps still resolve cleanly.

mlflow~=3.5
Lock Consistency

Ensure the new mlflow hashes match the wheels used on your target architectures and Python versions, and that the lock remains coherent with mlflow-skinny and other pinned packages to avoid resolution conflicts at build time.

mlflow==3.5.0 \
    --hash=sha256:138cd211eac787d0db80523f8f2456c562c6dd82b3eb912a2a42d96f3a9c4fa3 \
    --hash=sha256:ea06c79d933c30fe863cb7c809818c36f356e58a3f4007ab1f6c6c3b752c2b3e

@pull-request-agent
Copy link

PR Code Suggestions ✨

No code suggestions found for the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file PR title format python Pull requests that update python code Review effort 2/5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants