Change8

Migrating to MLflow v3.13.0rc0

Version v3.13.0rc0 introduces 2 breaking changes. This guide details how to update your code.

Released: 5/22/2026

2
Breaking Changes
2
Migration Steps
6
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

/mlflow/users/permissions/*`role_permissions``prompt` (as RBAC resource_type)`mlflow autolog claude``LiveSpan.add_link()`AI Gateway UI (for endpoint creation)

Breaking Changes

Issue #1

Legacy per-resource permission tables have been collapsed into the unified `role_permissions` structure as part of RBAC Phase 2. Existing permission configurations relying on the old table structure may need migration.

Issue #2

The legacy Python autolog hook for `mlflow autolog claude` is replaced by the new official plugin mechanism for coding agents. Users relying on the old hook must switch to the new plugin setup.

Migration Steps

  1. 1
    Review and update existing RBAC permission configurations to use the new `role_permissions` structure instead of legacy per-resource permission tables.
  2. 2
    Migrate from the legacy `mlflow autolog claude` Python hook to the new official plugin mechanism for Claude coding agent integration.

Release Summary

MLflow 3.13.0rc0 introduces a major overhaul of Role-Based Access Control (RBAC) with a new Admin UI, integrates several new coding agents via plugins in the AI Gateway, and provides a production-ready Helm chart for Kubernetes deployment.

Need More Details?

View the full release notes and all changes for MLflow v3.13.0rc0.

View Full Changelog