Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#49,128 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
azure, python

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Python
星标
5.6k
派生
3.4k
平均合并
1 天 18 小时
30 天内合并 PR
214

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Azure/azure-sdk-for-python 的其他 Issue

查看 Azure/azure-sdk-for-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。