Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Follow-up to #48745: azureml-mlflow 1.62.0.post6 still blocks mlflow >=3.15.3

Abierto
  • ¿Algo no está bien?
#49,128 1 comentario 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
azure, python
Área
cloud, machine-learning

Línea de trabajo

Start by reproducing dependency resolution with the MLflow and azureml-mlflow constraints listed in the issue, then inspect the azureml-mlflow package metadata for its mlflow-skinny upper bound. Done means determining a compatible release path for mlflow >=3.15.3 and addressing the requested guidance on the SDK v2 integration approach.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

azureml-mlflow Service Attention
  • Package Name: azureml-mlflow
  • Package Version: 1.62.0.post6
  • Operating System: Linux (Kubernetes workload)
  • Python Version: Python 3.11

Describe the bug

This is a follow-up to issue #48745.

First, thank you for releasing azureml-mlflow 1.62.0.post6. That release resolved the previous dependency blocker and allowed mlflow to be upgraded to 3.15.0.

However, a new security requirement now requires upgrading to:

  • mlflow >=3.15.3

When testing that requirement, dependency resolution is blocked again because azureml-mlflow 1.62.0.post6 still constrains mlflow-skinny to <=3.15.0.

Current dependency behavior:

  • azureml-mlflow 1.62.0.post6 requires mlflow-skinny <=3.15.0
  • The next available matching MLflow version appears to be mlflow 3.16.0
  • mlflow 3.16.0 requires mlflow-skinny 3.16.0

Because of this, mlflow >=3.15.3 cannot currently be resolved together with azureml-mlflow 1.62.0.post6.

The previous release successfully unblocked mlflow 3.15.0, but the current security remediation now needs support for a newer MLflow / MLflow Skinny dependency set.

To Reproduce

Steps to reproduce the behavior:

  1. Try to install or resolve dependencies with:

    mlflow >=3.15.3,<4.0.0
    azureml-mlflow >=1.62.0.post6,<2.0.0

  2. Dependency resolution fails because:

    mlflow 3.16.0 requires mlflow-skinny 3.16.0
    azureml-mlflow 1.62.0.post6 requires mlflow-skinny <=3.15.0

Expected behavior

azureml-mlflow should support a newer MLflow / MLflow Skinny dependency set that allows security-driven upgrades beyond mlflow 3.15.0.

Could you please confirm whether a new azureml-mlflow release is planned to support mlflow-skinny 3.16.0, or another MLflow version that satisfies mlflow >=3.15.3?

Screenshots

Not applicable.

Additional context

This is a follow-up to #48745.

Also, could you clarify the recommended long-term SDK v2-compatible approach for MLflow tracking and artifact/model registration with Azure ML?

Specifically:

  • Should teams continue using azureml-mlflow together with Azure ML SDK v2 for MLflow integration?
  • Or is there a planned SDK v2 replacement/equivalent for azureml-mlflow?

Thanks again for your help.

Lenguaje dominante
Python
Estrellas
5.6k
Forks
3.4k
Merge medio
1 d 18 h
PR fusionados (30 d)
214

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/azure-sdk-for-python

Todos los issues de Azure/azure-sdk-for-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.