[Translation] Bump azure-core minimum to 1.37.0 to fix mindependency check - #48313
Merged
Merged
Conversation
The mindependency CI check pins azure-core to the declared floor of 1.30.0, which conflicts with the azure-identity dev requirement of azure-core>=1.31.0. Resolution then falls back to fetching an older azure-identity from pypi.org, which is blocked on CI agents, so the check fails deterministically and the Build stage takes the Release stage down with it. Raise the floor to 1.37.0, matching the sibling azure-ai-translation-text package whose mindependency check passes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 1463e8ad-d7bf-45ad-aea2-c50defc1914b
|
Azure Pipelines: Successfully started running 1 pipeline(s). 9 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Raises the azure-core dependency floor to unblock the document translation package’s minimum-dependency validation and 2.0.0 release.
Changes:
- Requires
azure-core>=1.37.0, matching the sibling translation package. - Documents the dependency change in the 2.0.0 changelog.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
sdk/translation/azure-ai-translation-document/setup.py |
Updates the minimum azure-core version. |
sdk/translation/azure-ai-translation-document/CHANGELOG.md |
Records the dependency-floor increase. |
zhangeugenia
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the
mindependencyCI failure blocking theazure-ai-translation-document2.0.0 GA release.Problem
The
mindependencycheck pinsazure-coreto the declared floor (>=1.30.0→azure-core==1.30.0). That conflicts with the in-repoazure-identitydev requirement:Dependency resolution then falls back to fetching an older
azure-identity(1.25.3) from pypi.org, but CI agents install from an internal Azure Artifacts feed and block pypi.org egress:So the check fails deterministically. Because the
Release: azure-ai-translation-documentstage is gated onBuild, this blocks the release entirely.Reproduced on two consecutive runs of
python - translation:Both show
Total checks: 12 | Failed: 1, withmindependencythe sole failure and zero failing tests. All other checks (whl,sdist,import_all,latestdependency,whl_no_aio) pass.Fix
Raise the
azure-corefloor to>=1.37.0, matching the siblingazure-ai-translation-textpackage in the same service directory — which has the same localazure-identitydev requirement and whosemindependencycheck passes in the same pipeline run.Notes
>=1.31.0would be the minimal fix;1.37.0matches the sibling package for consistency, and 2.0.0 is a major version, so raising the floor is appropriate.