Prepare 10.8.1 servicing release#7646
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 725eeebf-4d23-444d-b6eb-5260d7492cd0
…se) encrypted reasoning (#7629) * Fix OpenAI Responses encrypted reasoning id round-trip for store=false resume The streaming path dropped the reasoning item's service assigned id, so on a stateless (store=false) resume the reconstructed reasoning item had no id and the Azure AI Foundry project scoped Responses endpoint rejected the request with HTTP 400 invalid_payload. RawRepresentation could not carry the id because it is [JsonIgnore] and does not survive session serialization between turns. Carry the reasoning item id in the reasoning content's AdditionalProperties, which survives both content coalescing and JSON serialization, and restore it on the outgoing request (handling both string and JsonElement values). Adds a streaming round-trip test that serializes and rehydrates the history to model a persisted human in the loop approval session. Refs #7628, microsoft/agent-framework#7067 * Use first-class TextReasoningContent.ItemId to roundtrip reasoning id Replaces the AdditionalProperties based carrier from the previous commit with a first class optional TextReasoningContent.ItemId property, marked [Experimental] (MEAI001). Content coalescing preserves it, and the OpenAI Responses client populates and consumes it, so the reasoning item id survives both coalescing and JSON serialization of the chat history and is sent back on stateless (store=false) resume. The typed, serializable property also removes the need to special case JsonElement values when reading the id back. The AdditionalProperties approach is kept in history (previous commit) for backtrack. Refs #7628, microsoft/agent-framework#7067 * Fix stale test comment to reference TextReasoningContent.ItemId The roundtrip test comment still referenced the AdditionalProperties carrier from the earlier commit; the current implementation roundtrips the reasoning item id via the TextReasoningContent.ItemId property. Addresses PR review feedback. Refs #7628, microsoft/agent-framework#7067 * Revert "Fix stale test comment to reference TextReasoningContent.ItemId" This reverts commit bc42d22. * Revert "Use first-class TextReasoningContent.ItemId to roundtrip reasoning id" This reverts commit 6fe9943. * Use named arguments for CreateReasoningContent encrypted-content call Pass protectedData and itemId by name at the streaming encrypted-content call site to avoid misreading the positional encrypted-content argument. No behavior change. --------- Co-authored-by: Tarek Mahmoud Sayed <tarekms@microsoft.com>
…chat history (#7617) * Address fcc/frc ordering bug when using approvals and service stored chat history * Address PR comments * Address PR comments
jeffhandley
enabled auto-merge (rebase)
July 20, 2026 23:25
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
4 participants
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.
Prepare the 10.8.1 servicing release for the following packages:
Commits included