chore(deps): bump openai-go/v3 to v3.61.0 - #4327
Merged
Merged
Conversation
ResponseStreamEventUnion.Name was removed in the new SDK; parse the top-level name from RawJSON() instead, falling back to Item.Name. Assisted-By: docker-agent Signed-off-by: David Gageot <david.gageot@docker.com>
docker-agent
left a comment
docker-agent
left a comment
Contributor
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
aheritier
added
status/needs-triage
gtardif
approved these changes
Sep 17, 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
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.
The openai-go v3 SDK removed
ResponseStreamEventUnion.Namebetween v3.54.0 and v3.61.0, which broke compilation. This bump upgrades the dependency and fixes the callsite.The response stream handler now reads the optional top-level event name directly from
event.RawJSON()instead of the removed field. Valid names take precedence over any per-item name; missing, null, empty, or non-string values fall back gracefully. A regression test covers the main cases including escaped names and buffered tool-argument flushing.No behavioural change is expected for correctly-formed streams; the fallback path only activates for events where the SDK no longer exposes the field.