Skip to content

Unpin azure-ai-agentserver-{core,invocations,responses} in Python hosted-agent samples - #931

Open
Nathandrake229 wants to merge 2 commits into
microsoft-foundry:mainfrom
Nathandrake229:unpin-agentserver-sdk-versions
Open

Unpin azure-ai-agentserver-{core,invocations,responses} in Python hosted-agent samples#931
Nathandrake229 wants to merge 2 commits into
microsoft-foundry:mainfrom
Nathandrake229:unpin-agentserver-sdk-versions

Conversation

@Nathandrake229

Copy link
Copy Markdown
Contributor

What

Unpin the ==<version> specifiers on the three azure-ai-agentserver-* packages (core, invocations, responses) across the Python hosted-agent samples so they install the latest published releases instead of being frozen on a specific preview build.

Only these three packages are unpinned. All other pinned dependencies (azure-ai-projects, azure-core, openai, azure-identity, etc.) are left unchanged. 62 files updated (requirements.txt, requirements.in, and one pyproject.toml).

Why

The three agentserver packages ship as a coordinated set and must stay version-aligned. Hard pins make a sample install a mismatched combination once one package moves ahead.

A concrete example this fixes: azure-ai-agentserver-responses==2.1.0b1 (the version several samples pin, directly or transitively) contains a hosted hard-fail branch that returns HTTP 500 (Resilient task subsystem missing in hosted environment) when paired with azure-ai-agentserver-core==2.1.0b2 — which is exactly what pip install ...responses==2.1.0b1 resolves to, because it pulls the latest satisfying core. The responses-side fix (swallow → run in-process) merged in Azure/azure-sdk-for-python#48591 but is not yet published, so the pinned samples cannot pick it up. Unpinning lets samples move to the fixed build automatically once it releases.

Scope

  • No functional/code changes — dependency specifiers only.
  • Lockfile-style requirements.txt files keep all other transitive pins; only the three agentserver lines are unpinned.

Remove the ==<version> pins on the three azure-ai-agentserver packages
across hosted-agent Python samples so they track the latest published
releases. This prevents samples from being stuck on a specific preview
build (e.g. responses==2.0.0b0 / core==2.1.0b1) that can fall out of sync
with the other packages.

Only the three agentserver packages are unpinned; all other pinned
dependencies are left unchanged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…mport

Pin azure-ai-agentserver-core/responses to 2.1.0b2 and invocations to
1.1.0b1 across the Python hosted-agent samples (replacing the unpinned
specifiers) so samples build against known-working SDK releases.

Move get_input_expanded to azure.ai.agentserver.responses.models in the
toolbox/browser-automation/langgraph responses samples; it was removed
from the top-level azure.ai.agentserver.responses package in 2.0.0+.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants