Repository navigation
Bump the azure-ai-agentserver group with 3 updates - #3
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Azure.AI.AgentServer.Core from 1.0.0-beta.29 to 1.0.0-beta.30 Bumps Azure.AI.AgentServer.Invocations from 1.0.0-beta.7 to 1.0.0-beta.8 Bumps Azure.AI.AgentServer.Responses from 1.0.0-beta.8 to 1.0.0-beta.9 --- updated-dependencies: - dependency-name: Azure.AI.AgentServer.Core dependency-version: 1.0.0-beta.30 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: azure-ai-agentserver - dependency-name: Azure.AI.AgentServer.Invocations dependency-version: 1.0.0-beta.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: azure-ai-agentserver - dependency-name: Azure.AI.AgentServer.Responses dependency-version: 1.0.0-beta.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: azure-ai-agentserver ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
This branch had an error being 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.
Updated Azure.AI.AgentServer.Core from 1.0.0-beta.29 to 1.0.0-beta.30.
Release notes
Sourced from Azure.AI.AgentServer.Core's releases.
1.0.0-beta.30
1.0.0-beta.30 (2026-10-15)
Features Added
POST /_agent/before-snapshotandPOST /_agent/after-restorelifecycle endpoints for memory snapshot capture and restoration, with
POST /_before_snapshotandPOST /_after_restoreas aliases. Applications can registeran
IAgentSnapshotLifecyclesingleton to release and rebuild process state; Core appliessession environment overrides first and provides serialized, idempotent retry handling.
Consumers acknowledge this experimental contract with the
AAAS002diagnostic.FoundryEnvironment.SessionInstanceId, sourced fromFOUNDRY_AGENT_SESSION_GUID, andvalidation of the hosted platform's 32-character lowercase hexadecimal session-incarnation ID.
TaskDefinition<TInput, TOutput>.GetStatusAsync()for task-ID migration and compatibilityprobes without activating or reclaiming the task.
TaskDefinition<TInput, TOutput>.TryStartExistingAsync()compatibilityprimitive, which starts a multi-turn task only if its record still exists and never enters the
create path.
SetResilientTasksEnabled()andResilientTaskOptions.Enabled. Task registration alone no longer initializes task storage orrecovery; enabled hosts run startup recovery and the periodic recovery loop.
IResilientTaskHandler<TInput, TOutput>registration overloads. The task engine createsand asynchronously disposes a fresh dependency-injection scope for every execution
attempt, including retries, steered turns, and recovered attempts.
IHostApplicationBuilder.AddAgentEventStreams(sectionName). Explicit applicationconfiguration now overrides protocol defaults regardless of registration order,
identical selections are idempotent, and conflicting same-precedence selections fail
with source diagnostics instead of silently discarding durability settings.
TaskContext<TInput>.Stream, and callers subscribe throughTaskRun<TOutput>.Stream.Streams use the per-turn
InputId, remain open across retry and recovery deferral, andclose only after the existing terminal task-store transition succeeds.
ResilientTaskSettings : ClientSettingsand configuration-boundIHostApplicationBuilder.AddResilientTasks(sectionName)overloads. Hosted task storagenow accepts its credential and project endpoint from one settings object.
Breaking Changes
SetResilientTasksEnabled()before host startup. Starting a registered task while disabledthrows
ResilientTaskExceptionwithResilientTaskErrorCode.NotEnabled.UseInMemoryReplay()now defaults to a bounded 10-minute retention window instead ofretaining closed streams indefinitely.
Azure.ETagtype.This includes
StateStoreItem.Etag,StateStoreItemRef.Etag,StateStoreItemKey.Etag,FoundryStoragePreconditionException.CurrentETag, thecorresponding model-factory parameters, and
FoundryStateStore.SetItemAsync/DeleteItemAsyncifMatchparameters.Bugs Fixed
... (truncated)
Commits viewable in compare view.
Updated Azure.AI.AgentServer.Invocations from 1.0.0-beta.7 to 1.0.0-beta.8.
Release notes
Sourced from Azure.AI.AgentServer.Invocations's releases.
1.0.0-beta.8
1.0.0-beta.8 (2026-10-28)
Features Added
VoiceInputDataPart, orderedVoiceUserMessageEvent.ContentParts, andVoiceResponseOutputDataDoneMessagefor application data in Bridge protocol1.0. The existing text-onlyContentprojection and explicit silent completion remain available./voice_conversation_engineWebSocket route for typed Voicehandlers registered with
AddVoice<THandler>(). It reuses the existing BridgeProtocol 1.0 relay alongside
/invocations_ws, without new registration optionsor changes to generic Invocations handlers.
user.barge_in,VoiceUserBargeInEvent, andOnUserBargeInAsync, preserving playback snapshots and application-owned cancellation/history. Voice Live senders must use the same event contract. Generic raw WebSocket handlers are unchanged.Other Changes
Azure.AI.AgentServer.Core1.0.0-beta.30 package instead of the current Core project, so this release does not require publishing Core 1.0.0-beta.31.SetResilientTasksEnabled()explicitly; taskregistration alone no longer activates storage or recovery.
task-bound producer/consumer streams, while retaining registry lookup for later GET
replay by invocation id.
Commits viewable in compare view.
Updated Azure.AI.AgentServer.Responses from 1.0.0-beta.8 to 1.0.0-beta.9.
Release notes
Sourced from Azure.AI.AgentServer.Responses's releases.
1.0.0-beta.9
1.0.0-beta.9 (2026-10-15)
Features Added
FOUNDRY_AGENT_SESSION_GUID, preventingrecreated sessions from reusing name-derived IDs that refer to tombstoned tasks from an earlier
incarnation and can cause a service precondition failure (HTTP 412).
Public
ResponseContext.ConversationChainIdvalues and one-shot task IDs are unchanged, andpending, in-progress, or suspended pre-rollout chains continue under their legacy task IDs.
AddResponsesServer(IHostApplicationBuilder host, string sectionName)andAddResponsesServer(IHostApplicationBuilder host, string sectionName, Action<ResponsesServerSettings>),which bind a new
ResponsesServerSettings : ClientSettings(the Foundry credential,Endpoint,and option flags) from a single configuration section. Because response storage and
resilient-task storage bind the same identity and endpoint from one section, the two cannot
diverge. This is the required entry point in hosted Foundry environments. In a hosted
container, values the section does not provide default to the platform:
EndpointtoFOUNDRY_PROJECT_ENDPOINT, and an absentCredentialsection to aDefaultAzureCredentiallimited by default to the production credentials (environment, workload identity and managed
identity;
AZURE_TOKEN_CREDENTIALSoverrides the selection), soResponsesServer.Run<THandler>()needs no configuration. ACredentialsection that does notresolve still fails startup.
ResponseContext.ClientCancellation(aCancellationToken) alongsideResponseContext.Shutdown, so an explicit client cancel is composable as a token.Breaking Changes
ResilientBackground=trueenables it automatically; otherwisestore=truerequests executein-process and are not recovered after an ungraceful crash.
responses/partitions-v1namespace.Previously persisted responses and their history are not visible after upgrade, including
for anonymous requests and crash recovery. Legacy files remain unchanged; there is no
automatic migration or legacy read fallback. Restoring old data requires an explicit,
operator-controlled migration with independently verified ownership. Newly persisted
partitioned data continues to survive restarts.
ClientSettingspattern. TheAddResponsesServer(IServiceCollection, Action<ResponsesServerOptions>)overload remains forlocal / non-hosted scenarios and now throws in a hosted Foundry environment (use the
IHostApplicationBuilderoverload there). The internalDEFAULT_FETCH_HISTORY_ITEM_COUNTenvironment-variable read and the ambient
TokenCredentialregistration were removed(
FOUNDRY_PROJECT_ENDPOINTis now only the fallback for an unconfiguredResponsesServer:Endpoint); the HTTPS-in-non-development check now honorsIHostEnvironment.IsDevelopment()rather than readingASPNETCORE_ENVIRONMENT/DOTNET_ENVIRONMENTdirectly.ResponseEventStream.Checkpoint()was renamed to the virtualCreateCheckpointEvent(), andResponseEventStream.InternalMetadatawas renamed toPersistedMetadata.ResponseContext.ClientCancelledwas renamed toIsClientCancelled.IsShutdownRequestedandIsClientCancelledare now get-only virtual passthroughs over theShutdown/ClientCancellationtokens; the settableIsShutdownRequestedwas removed.Bugs Fixed
... (truncated)
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions