fix(deps): update dependency @openai/agents-core to ^0.17.0 - #4492
fix(deps): update dependency @openai/agents-core to ^0.17.0#4492renovate[bot] wants to merge 1 commit into
Conversation
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Changed Packages
|
3f3d7ab to
e1f1136
Compare
|
❌ The last analysis has failed. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4492 +/- ##
=========================================
Coverage 61.61% 61.61%
=========================================
Files 2568 2568
Lines 102824 102824
Branches 28800 28801 +1
=========================================
Hits 63360 63360
+ Misses 38913 37649 -1264
- Partials 551 1815 +1264
*This pull request uses carry forward flags. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
some manual verification with our llamastack agentic chat test case is required here |
This PR contains the following updates:
^0.14.0→^0.17.0Release Notes
openai/openai-agents-js (@openai/agents-core)
v0.17.0Compare Source
Key Changes
Output-guardrail replay safety
Serialized output-bearing approval checkpoints now fail closed with
UserErrorwhen the SDK cannot prove which response owns a pending terminal tool output. Continue with the liveRunStatewhen possible, or start a new run from safe input instead of replaying ambiguous serialized items. When an output guardrail rejects a completed function-tool result used as final output, the SDK replaces rejected content in SDK-owned replay surfaces withOutput withheld by an output guardrail., sanitizes current guardrail metadata, and preserves earlier accepted history. This does not undo external tool side effects or erase application-owned copies.Complete guardrail batch results
Guardrails started in the same batch now settle before the runner surfaces a tripwire or execution failure. Completed sibling results remain available in run state while further run processing is halted.
Explicit OpenAI client configuration
OpenAIProvidernow rejectsorganizationorprojectwhenopenAIClientis also supplied because provider-level values cannot modify an already-created client. Configure these values when constructing theOpenAIclient, then pass that client throughopenAIClient.What's Changed
Documentation & Other Changes
New Contributors
Full Changelog: openai/openai-agents-js@v0.16.1...v0.17.0
v0.16.1Compare Source
What's Changed
Documentation & Other Changes
Full Changelog: openai/openai-agents-js@v0.16.0...v0.16.1
v0.16.0Compare Source
Key Changes
Deterministic SDK testing utilities
This release adds provider-neutral testing utilities through
@openai/agents/testing,@openai/agents-core/testing,@openai/agents/realtime/testing, and@openai/agents-realtime/testing.ScriptedModel,scriptedSandboxSession(), andScriptedRealtimeTransportlet applications exercise runner, sandbox, and Realtime workflows without live model, sandbox, WebRTC, or WebSocket dependencies. Existing runtime entry points and defaults remain unchanged.Standard Schema inputs and outputs
Tools, handoffs, and agent structured outputs now accept supported Standard Schema values alongside Zod and raw JSON Schema. The schema must provide synchronous
~standard.validatebehavior plus~standard.jsonSchema.input()and~standard.jsonSchema.output(), and generated schemas must have an object root. Standard Schema function-tool parameters require strict mode; use a Zod schema, raw JSON Schema, or application-side validation for unsupported cases.Safer run, provider, and Realtime behavior
CallModelInputFiltercan opt into stable prepared-item identity withpreserveInputIdentity = true; default filters continue to receive deep copies, and the SDK does not freeze opted-in items. The release also tightens interruption snapshots, max-turn finalization, invalid tool-output redaction, Responses parallel-tool-call forwarding, Chat Completions reasoning placement, Realtime audio-rate fallback, and unsupported assistant-audio history replay handling.What's Changed
Documentation & Other Changes
New Contributors
Full Changelog: openai/openai-agents-js@v0.15.0...v0.16.0
v0.15.0Compare Source
Key Changes
OpenAI client compatibility and the new default model
This release requires
openai7.2 or later for applications that supply their own OpenAI client. Agents without an explicit model now usegpt-5.6-lunawithreasoning.effort: "none"andtext.verbosity: "low". Configure an explicit model or setOPENAI_DEFAULT_MODELwhen an application needs a different default.MCP v2 negotiation with legacy server support
Local MCP connections now use the MCP TypeScript SDK v2 client and negotiate the 2026-07-28 protocol where available, with compatible fallback for existing v1 servers. Applications using
MCPServerStdio,MCPServerStreamableHttp, orMCPServerSSEdo not need to bridge the v1 and v2 SDK packages themselves.Durable input, tool output, and retry state
RunState.addInput()can stage new input while a run is paused, andpendingInputsurvives serialization until the next safe model request. JSON-compatible tool return values retain their structure acrossRunStateserialization, while canonical invocation evidence prevents approved or completed local tool calls from being rebound incorrectly. Applications may explicitly approve an otherwise unsafe non-streaming model replay withapproveUnsafeReplay: true.Safer sandbox mount credentials
Credential-bearing in-container mounts now fail closed unless the application acknowledges the exact effective mount path with
Manifest.withInContainerMountCredentialExposureAcknowledged()or, for ambient and external authority,Manifest.withInContainerMountBroadCredentialExposureAcknowledged(). Serialized credentials and unsafe mount authority are never trusted on resume. The deprecated VercelallowS3CredentialExposure: trueoption remains available for released inline S3 configurations.React Native and Realtime improvements
Core and Realtime packages now publish React Native conditions for portable shims. React Native applications provide an app-owned native WebRTC transport and retain responsibility for permissions, audio routing, and transport lifecycle. Realtime configuration also supports GA transcription models and context options, while closing browser WebRTC transports no longer stops caller-owned media streams.
More faithful provider and adapter results
The OpenAI and AI SDK adapters now preserve additional provider behavior across streaming and non-streaming runs, including Chat Completions audio, citations and request IDs, optional raw usage, AI SDK PDF inputs and prompt-cache retention, conversation program item IDs, apply-patch move destinations, and complete interleaved output ordering.
What's Changed
Documentation & Other Changes
New Contributors
Full Changelog: openai/openai-agents-js@v0.14.3...v0.15.0
v0.14.3Compare Source
What's Changed
Documentation & Other Changes
Full Changelog: openai/openai-agents-js@v0.14.2...v0.14.3
v0.14.2Compare Source
What's Changed
Documentation & Other Changes
Full Changelog: openai/openai-agents-js@v0.14.1...v0.14.2
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.