Skip to content

Python: raise Content Understanding dependency floor to 1.2.0b3 - #9695

Merged
Eduard van Valkenburg (eavanvalkenburg) merged 1 commit into
microsoft:mainfrom
sunny-kavixo:fix/9693-contentunderstanding-floor
Oct 26, 2026
Merged

Eduard van Valkenburg (eavanvalkenburg) merged 1 commit into
microsoft:mainfrom
sunny-kavixo:fix/9693-contentunderstanding-floor

Conversation

@sunny-kavixo

Copy link
Copy Markdown
Contributor

Motivation & Context

The azure-contentunderstanding package declares azure-ai-contentunderstanding>=1.2.0b2,<2, but its implementation calls to_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

  • What are the major changes? Raise the Azure Content Understanding lower bound to 1.2.0b3 and synchronize the workspace lock metadata.
  • What is the impact of these changes? Installs now use the first SDK version that supports the provider’s existing custom_metadata call, preserving the current public behavior without source workarounds.
  • What do you want reviewers to focus on? The dependency floor is the smallest compatibility fix; no provider source or test behavior was changed.

Related Issue

Fixes #9693

AI Assistance

  • This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

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

  • The code builds clean without any errors or warnings
  • All unit tests pass, and I have added new tests where possible
  • The PR follows the Contribution Guidelines
  • This PR links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
  • This is not a breaking change.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 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 <2 upper 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

This was referenced Nov 2, 2026

This branch was previously deployed

1 inactive deployment
github-app-auth — 194b2612 Deployed Oct 26, 2026 by sunny-kavixo via team_check #7448
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

python Usage: [Issues, PRs], Target: Python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dependency bounds test failed

3 participants