Prepare azure-ai-agentserver-invocations 1.0.0b8 release - #48398
Merged
Shiva S (Shivakishore14) merged 1 commit intoAug 3, 2026
Merged
Conversation
Date the 1.0.0b8 CHANGELOG entry (2026-08-03) and bump the minimum azure-ai-agentserver-core dependency to >=2.0.0b10, which adds the opt-in gate for resilient-task startup recovery so invocations-only agents no longer make a blocking task-store call during startup. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5222ab61-7d5e-4642-b75f-ef365e375f4f
Nathandrake229
requested review from
Ravi Pidaparthi (RaviPidaparthi),
Shiva S (Shivakishore14),
Ankit Sinha (ankitbko) and
Pranav Pandit (vangarp)
as code owners
August 3, 2026 03:15
|
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
Prepares azure-ai-agentserver-invocations 1.0.0b8 for release.
Changes:
- Dates the 1.0.0b8 release entry.
- Requires
azure-ai-agentserver-core>=2.0.0b10. - Documents the startup-recovery improvement.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
pyproject.toml |
Updates the minimum core dependency. |
CHANGELOG.md |
Dates and documents the release. |
Shiva S (Shivakishore14)
approved these changes
Aug 3, 2026
Shiva S (Shivakishore14)
deleted the
namantyagi/agentserver-invocations-responses-release-prep
branch
August 3, 2026 04:28
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.
Summary
Release preparation for azure-ai-agentserver-invocations 1.0.0b8.
Changes
1.0.0b8CHANGELOG entry —## 1.0.0b8 (Unreleased)→## 1.0.0b8 (2026-08-03).azure-ai-agentserver-coredependency from>=2.0.0b9to>=2.0.0b10inpyproject.toml.2.0.0b10adds an opt-in gate for resilient-task startup recovery, so invocations-only agents no longer make a blocking task-store (GET /tasks) call during startup.Why
azure-ai-agentserver-core==2.0.0b10(published to PyPI) ships the opt-inTaskManagerstartup gate that fixes a startup-latency regression: previously every hosted agent — including invocations-only agents that never declare a durable task — made a blocking task-store call at container startup. Raising the floor to>=2.0.0b10guarantees invocations users pick up that fix even if they pinazure-ai-agentserver-core.Validation
pyproject.tomlparses; resolved dependencies:['azure-ai-agentserver-core>=2.0.0b10', 'aiohttp>=3.10.0,<4.0.0a0']._version.py=1.0.0b8(matches the dated CHANGELOG entry).>=2.0.0b9floor references remain in the package.2.0.0b10behavior (recovery deferred when no task is declared and the flag is off; recovery runs when a task is declared or the flag is set) was validated end-to-end against the published package on a live West US 2 deployment.