1.0.0-beta.5 (2026-05-21)
Features Added
- Replaced
invoke_agentSERVER span with baggage-only propagation. W3C trace context propagation is now handled automatically by ASP.NET Core, so handler spans are parented directly under the caller's span. - Response ID, conversation ID, and streaming mode are propagated as Activity baggage for downstream correlation.
- Simplified
ResponsesActivitySourceto focus on baggage propagation rather than span creation. - All error responses (4xx/5xx) now include the
x-platform-error-sourceheader classifying
error origin asuser(invalid request),platform(SDK/infrastructure failure), or
upstream(developer handler failure) per container-image-spec §8. - Platform errors include the
x-platform-error-detailheader with full exception context
(type, message, stack trace) for diagnostic telemetry.AggregateExceptionwrappers are
unwrapped and the detail is truncated to 2048 characters. - Foundry storage pipeline exceptions are now tagged as platform errors at the source, enabling
accurate classification of storage transport, authentication, and service failures regardless
of exception type.
Bugs Fixed
- Enabled automatic gzip/deflate/brotli decompression on the Foundry storage HTTP pipeline.
Intermediary gateways or load-balancers that return compressed responses are now handled
transparently, preventing JSON parse failures on raw gzip bytes. The pipeline also
advertisesAccept-Encodingsupport so servers can compress responses proactively.