React to OpenAI upcoming release 2.10.1 or 2.11.0

[ericstj]

🔴 OpenAI SDK Upcoming Release — Compensating Work Required

See dedicated section below. Summary: openai/openai-dotnet PR #1129 "Split Responses" (3065 files) merged 2026-04-30; next release forecast ~2026-05-09–12. MEAI.OpenAI's OpenAIResponsesChatClient will require compensating changes.

Customer-Impacting Bugs

Title	URL	Age	Labels
OpenAI Responses API streaming responses are missing MessageID on function calls	#7479	13d	untriaged, bug, area-ai
FunctionInvokingChatClient reorders messages with FunctionApprovalResponseContent	#7156	140d	untriaged, bug, area-ai (also stale)
SemanticSimilarityChunker ignores MaxTokensPerChunk, throws input-length exception	#7297	81d	bug, area-data-ingestion
Streaming with Vertex AI produces empty parts in tool-calling follow-up (regression in Google.GenAI 1.6.1)	googleapis/dotnet-genai#273	32d	type: bug, priority: p2

Issue #7479 is particularly high-impact: streaming Responses API is a high-traffic code path; missing MessageID breaks multi-turn conversation tracking for users of OpenAIResponsesChatClient.

---

OpenAI SDK: Upcoming Changes & Release Forecast

🚨 OpenAI .NET SDK release expected by ~2026-05-12 — the Responses API has been structurally refactored on main. Confirm compensating MEAI.OpenAI changes are planned and in flight before this release ships.

Noteworthy upcoming PRs (merged since 2.10.0 or currently open, touching API surface consumed by MEAI.OpenAI):

PR	Status	Why it matters for MEAI.OpenAI	Impact
#1129 Split Responses	merged 2026-04-30	3,065-file restructure of the Responses API across the library — namespace and type topology changes; OpenAIResponsesChatClient directly consumes these types	🔴 breaking — compensating change required
#1135 Update streaming models for Responses	draft	Streaming type updates for Responses; MEAI.OpenAI streams Responses for GetStreamingResponseAsync	🔴 breaking — compensating change required once merged
#1147 Standardize enums to unions	open	Changes enum-typed API surface to extensible union types — API usage patterns in MEAI.OpenAI adapters may need updates	🟡 may require integration update
#1152 Standardize pagination and collection option types	open	API shape changes on paginated result types; MEAI.OpenAI may iterate over these	🟡 may require integration update
#1144 Rename Responses DI extensions	merged 2026-04-30	Renames OpenAIResponsesHostBuilderExtensions; affects any DI setup code in MEAI.OpenAI or samples	🟡 may require integration update
#1143 Add top-level ResponsesClient factory on OpenAIClient	merged 2026-04-30	New OpenAIClient.GetResponsesClient() factory — MEAI.OpenAI could expose this via AsIChatClient() overloads	🟢 opportunity only
#1142 Internalize OpenAIResponsesModelFactory	merged 2026-04-30	Removes OpenAIResponsesModelFactory from public API — breaks any MEAI.OpenAI test/production code referencing it	🔴 breaking — compensating change required if referenced
#1138 Rename ContainerClient file upload methods to UploadContainerFile	open (merged to #1139)	Upload API surface rename	🟡 low risk unless MEAI.OpenAI wraps container upload
#1132 Remove typed ProcessMessageAsync methods	open	Removes typed overloads from Assistants/Responses; MEAI.OpenAI may call these	🟡 may require integration update
#889 Factor Responses into its own assembly	open (dirty, 182 files)	Original Responses-factoring PR; may be superseded by #1129 or re-targeted — if merged, would require adding an OpenAI.Responses package reference to MEAI.OpenAI.csproj	🔴 if merged, new assembly reference required
#1099 Validate Experimental attributes for non-GA APIs	merged 2026-04-14	Enforces [Experimental] on non-GA types — MEAI.OpenAI's experimental API surface may need annotation review to avoid new warnings	🟡 may require integration update

Next release forecast

• Latest published version: 2.10.0 (released 2026-04-04) — NuGet · Release notes

• MEAI.OpenAI currently pins: OpenAI (no explicit version in csproj; central packages upgraded to 2.10.0 via Upgrade to OpenAI 2.10.0 #7450, merged 2026-04-08) — up to date

• Recent release cadence (stable releases):

  Release	Date	Days since prior
  2.6.0	2025-10-31	—
  2.7.0	2025-11-13	13
  2.8.0	2025-12-11	28
  2.9.0	2026-02-27	78
  2.9.1	2026-03-02	3 (patch)
  2.10.0	2026-04-04	33

  Average interval (minor releases, excl. patch): ~38 days; median: ~31 days.

• Anticipated next release: ~2026-05-09–2026-05-12 (31–38 days after 2.10.0)

• Confidence: medium — strong signal from merged structural changes; no explicit release branch or draft GitHub Release observed, but the pace of main merges in late April (Responses split, DI renames, factory additions) is consistent with release-preparation activity.