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

azureml-mlflow 1.62.0.post5 dependency constraints block required mlflow and cryptography security upgrades

Abierto
  • ¿Algo no está bien?
#48,745 12 comentarios 1 reacción 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@saanikaguptamicrosoft ya está trabajando en esto.

Desde el 26/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Client customer-reported Machine Learning needs-team-attention question Service Attention
  • Package Name: azureml-mlflow
  • Package Version: 1.62.0.post5
  • Operating System: Linux (Kubernetes workload)
  • Python Version: 3.11

Describe the bug

We use azureml-mlflow for remote MLflow tracking against an Azure Machine Learning Workspace from a Kubernetes workload.

The latest available version, azureml-mlflow 1.62.0.post5, currently introduces dependency constraints that prevent us from applying required security upgrades:

  • mlflow-skinny <= 3.13.0
  • cryptography < 49.0.0

Our security scanning requires:

  • mlflow >= 3.15.0
  • cryptography >= 50.0.0

Because azureml-mlflow is required for our azureml:// MLflow tracking URI, removing the package is not currently an option without changing the Azure ML tracking architecture.

To Reproduce

  1. Create a Python 3.11 environment.
  2. Install or declare azureml-mlflow==1.62.0.post5.
  3. Attempt to resolve the environment with mlflow>=3.15.0.
  4. Attempt to resolve the environment with cryptography>=50.0.0.
  5. The dependency resolver cannot satisfy these requirements together with the constraints introduced by azureml-mlflow.

Expected behavior

There should be a supported version of azureml-mlflow that is compatible with current secure versions of MLflow and its dependencies, or documented guidance for customers who need to remediate these dependency vulnerabilities while continuing to use an Azure Machine Learning Workspace as the remote MLflow tracking backend.

Screenshots

N/A

Additional context

Our application already uses Azure Machine Learning SDK v2 (azure-ai-ml / MLClient) to access the workspace.

MLflow is used for experiment tracking, metrics, parameters, artifacts, and model registry operations against the Azure ML Workspace.

According to the current Azure ML documentation, azureml-mlflow is still required when configuring remote MLflow tracking against an Azure Machine Learning Workspace from compute outside Azure ML.

Could you please confirm:

  1. Whether a new azureml-mlflow release is planned that relaxes these dependency constraints.
  2. Whether there is a currently supported alternative that allows us to keep Azure ML Workspace as the MLflow tracking backend while upgrading MLflow.
  3. What the recommended remediation path is for customers blocked from security upgrades by these constraints.
Lenguaje dominante
Python
Estrellas
5.6k
Forks
3.4k
Merge medio
2 d 1 min
PR fusionados (30 d)
218

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.