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

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

Aperta
  • Qualcosa non va?
#49,128 1 commento 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
azure, python
Ambito
cloud, machine-learning

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
5.6k
Fork
3.4k
Merge medio
1g 18h
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.