Repository navigation
fix(core): exclude invalid Bedrock entries from models.dev imports - #48081
Merged
Merged
Conversation
rekram1-node
changed the title
rekram1-node
changed the title
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.
Follow-up to #48078.
Move the exclusion into the existing models.dev plugin: skip an imported model when its provider is Bedrock and
model.modelID ?? model.idmatches the 13-entry list. User configuration runs afterward normally.Remove the old Bedrock-plugin filter. Keep Opus 4.6 and Sonnet 4.6, which AWS documents as supporting in-region Runtime calls in London (
eu-west-2).Removed the added regression test. Updated the existing Nova reasoning fixture to its working US profile and removed the obsolete Bedrock-filter tests.
Sources:
Checks: existing models.dev tests (12 passing), Core
bun typecheck, Prettier, andgit diff --checkpass.