You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Align workflow/agentworkflow response merging with the upstream .NET workflow-hosting fix from microsoft/agent-framework#7123 (05834b56e31f941e90e3337eb0f09d1a6ad8ee88).
The Go port keeps workflow-agent message ordering in first-seen order by:
preserving first-seen response/message grouping instead of re-sorting merged messages by timestamp,
keeping identifierless update segments in their original position instead of appending all dangling updates at the end,
preserving per-message CreatedAt values when stamping merged messages.
It also adds focused parity tests for the ordering cases that regressed upstream: contiguous response ordering, function call/result ordering, and identifierless segment handling.
Added workflow/agentworkflow/message_merger_test.go parity coverage for first-seen ordering, contiguous response grouping, function call/result ordering, and identifierless segments
Notes
This port is intentionally scoped to the shared Go message-merging behavior and does not add any public API.
The .NET PR also added handoff-orchestration coverage; Go does not have the corresponding handoff builder/executor surface yet, so this PR ports the shared ordering fix and its direct parity tests.
This was originally intended as a pull request, but GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch copilot/dotnet-port-fixes-message-ordering-20260716-af0566627077a9c6.
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Summary
Align
workflow/agentworkflowresponse merging with the upstream .NET workflow-hosting fix from microsoft/agent-framework#7123 (05834b56e31f941e90e3337eb0f09d1a6ad8ee88).The Go port keeps workflow-agent message ordering in first-seen order by:
CreatedAtvalues when stamping merged messages.It also adds focused parity tests for the ordering cases that regressed upstream: contiguous response ordering, function call/result ordering, and identifierless segment handling.
Ported .NET PRs
Upstream commit:
05834b56e31f941e90e3337eb0f09d1a6ad8ee88Breaking Changes
No.
Tests and Examples
go test ./workflow/agentworkflow/...workflow/agentworkflow/message_merger_test.goparity coverage for first-seen ordering, contiguous response grouping, function call/result ordering, and identifierless segmentsNotes
Note
This was originally intended as a pull request, but GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch
copilot/dotnet-port-fixes-message-ordering-20260716-af0566627077a9c6.Click here to create the pull request
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Show patch preview (314 of 314 lines)