Repository navigation
Python: raise Content Understanding dependency floor to 1.2.0b3 - #9695
Merged
Eduard van Valkenburg (eavanvalkenburg) merged 1 commit intoOct 26, 2026
Conversation
Putluru Sandeep (sunny-kavixo)
requested review from
SergeyMenshykh,
Tao Chen (TaoChenOSU),
Eduard van Valkenburg (eavanvalkenburg),
Giles Odigwe (giles17),
Jose Alvarez (jpalvarezl),
Evan Mattson (moonbox3),
Roger Barreto (rogerbarreto),
sophia-ramsey and
westey (westey-m)
as code owners
October 26, 2026 07:21
Putluru Sandeep (sunny-kavixo)
temporarily deployed
to
github-app-auth
October 26, 2026 07:21 — with
GitHub Actions
Inactive
Putluru Sandeep (sunny-kavixo)
temporarily deployed
to
github-app-auth
October 26, 2026 07:21 — with
GitHub Actions
Inactive
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The two-line compatibility fix is consistent across both declarations, matches the already-locked SDK version, and has no identified blocking issues.
No open issues 🎉
What changed in this PR
Raises the Azure Content Understanding SDK minimum to 1.2.0b3, aligning the dependency declaration with the provider’s existing custom_metadata usage and addressing the dependency-bounds failure in #9693.
Changes:
- Raises the SDK lower bound while retaining the
<2upper bound. - Synchronizes workspace lock metadata without changing provider source or test behavior.
| File | Description |
|---|---|
python/uv.lock |
Updates the dependency requirement to match the new minimum. |
python/packages/azure-contentunderstanding/pyproject.toml |
Raises the SDK minimum from 1.2.0b2 to 1.2.0b3. |
Review effort: Balanced
Eduard van Valkenburg (eavanvalkenburg)
approved these changes
Oct 26, 2026
This was referenced Oct 30, 2026
This was referenced Nov 2, 2026
Bump the dotnet-dependencies group with 16 updates
emrekarakas/enterprise-agent-orchestration-kit#11
Open
This branch was previously deployed
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.
Motivation & Context
The
azure-contentunderstandingpackage declaresazure-ai-contentunderstanding>=1.2.0b2,<2, but its implementation callsto_llm_input(..., custom_metadata=...), a keyword that is not available in the declared lower-bound SDK. The lowest-direct dependency-bounds run therefore failed 29 tests, including file-search, pending-session, warnings, and category coverage.Description & Review Guide
1.2.0b3and synchronize the workspace lock metadata.custom_metadatacall, preserving the current public behavior without source workarounds.Related Issue
Fixes #9693
AI Assistance
AI assistance details: Investigation, dependency analysis, CI workflow preparation, and PR description were AI-assisted; the submitted dependency change was reviewed against the repository source and remote test evidence.
Contribution Checklist