Repository navigation
chore(ci): merge daily internal staging branch #33335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
yuneng-berri
merged 13 commits into
litellm_internal_staging
from
litellm_oss_daily_2026_07_10
Jul 15, 2026
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
49d655d
Merge pull request #31384 from BerriAI/litellm_internal_staging
yuneng-berri a311f11
Merge pull request #31477 from BerriAI/litellm_internal_staging
yuneng-berri 0ade44f
Merge pull request #31542 from BerriAI/litellm_internal_staging
shivamrawat1 88e03e5
Merge pull request #31765 from BerriAI/litellm_internal_staging
yuneng-berri badc141
Merge pull request #32027 from BerriAI/litellm_internal_staging
yuneng-berri 79a6b8f
Merge pull request #32156 from BerriAI/litellm_internal_staging
yuneng-berri 9996378
Merge pull request #32400 from BerriAI/litellm_internal_staging
yuneng-berri f824783
Merge pull request #32663 from BerriAI/litellm_internal_staging
shin-berri 3d63eda
Merge pull request #32709 from BerriAI/litellm_internal_staging
yuneng-berri d7585cd
fix(proxy): route master key to team-scoped models (#32926)
kunal2002 75faed1
fix(bedrock_mantle): route xai.grok-4.3 via /openai/v1 frontier path …
marty-sullivan 90f495f
chore(ci): sync litellm_internal_staging into daily OSS branch (#33337)
yuneng-berri 6372ca3
Revert "chore(ci): sync litellm_internal_staging into daily OSS branc…
yuneng-berri File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The added error message explicitly refers to "teams" and proxy-level routing guidance ("Specify the deployment ID directly to disambiguate"), which are proxy concepts. Per the project rule, proxy-facing error messages should not live in
router.pybecause it is also an SDK component. While the code is only reachable today wheninclude_team_models=True(a flag only the proxy sets), placing the messaging here still embeds proxy semantics in the SDK layer and would affect SDK users who independently reach this path in the future.Rule Used: Don’t add stuff to router.py that is error message... (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!