Unpin azure-ai-agentserver-{core,invocations,responses} in Python hosted-agent samples - #931
Open
Nathandrake229 wants to merge 2 commits into
Open
Conversation
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>
Nathandrake229
had a problem deploying
to
L4-validation
August 21, 2026 04:22 — with
GitHub Actions
Failure
…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>
Nathandrake229
had a problem deploying
to
L4-validation
August 21, 2026 07:07 — with
GitHub Actions
Failure
Shanmukha Pasumarthy (shanmukha1200)
approved these changes
Aug 21, 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.
What
Unpin the
==<version>specifiers on the threeazure-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 onepyproject.toml).Why
The three
agentserverpackages 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 withazure-ai-agentserver-core==2.1.0b2— which is exactly whatpip install ...responses==2.1.0b1resolves 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
requirements.txtfiles keep all other transitive pins; only the three agentserver lines are unpinned.