Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#48,745 12 commenti 1 reazione 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@saanikaguptamicrosoft ci sta già lavorando.

Dal 26/8/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.
Lingua principale
Python
Stelle
5.6k
Fork
3.4k
Merge medio
2g 4h
PR unite (30g)
214

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Azure/azure-sdk-for-python

Tutte le issue di Azure/azure-sdk-for-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.