fix(ai): default native Mantle to Responses - #45394
Merged
Merged
Conversation
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
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.
Summary
AmazonBedrockMantle.configure(...).model(...)and both default native package exports use Responses, matching the native OpenAI convention.chat(...)and.responses(...)methods and their separate native entrypoints/protocolsOnly the default aliases change in production code. Callers using the default entrypoint for Chat-only models must select Chat explicitly; Core already selects the explicit Chat entrypoint for
openai.gpt-oss-safeguard-20bandopenai.gpt-oss-safeguard-120b. No models.dev, authentication, metadata, or routing-abstraction changes.Verification
bun typecheckpassed inpackages/aiandpackages/coregit diff --checkpassedv2at5b25ee8430