-
-
Notifications
You must be signed in to change notification settings - Fork 11.2k
[litellm-agent] Staging → litellm_internal_staging (5/11/2026) #27661
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
Closed
oss-pr-review-agent-shin
wants to merge
5
commits into
litellm_internal_staging
from
shin_agent_oss_staging_05_11_2026
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
db687bf
fix(ollama): Include provider in model list for ollama (#26135)
jamesmyatt 764c128
fix(ollama): process both thinking and content in same streaming chun…
vhash0 d1dbd57
fix(health_check): skip max_tokens for image_generation mode (#26417)
kimsehwan96 519cb4a
fix(http_handler): handle RequestNotRead in MaskedHTTPStatusError for…
dawidkulpa 5445377
Merge origin/litellm_internal_staging into shin_agent_oss_staging_05_…
Sameerlite 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
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.
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.
health_check_max_tokensno longer auto-enables injection on non-chat modesPreviously, setting
health_check_max_tokens: 50on any deployment (includingmode: image_generation) would cause that value to be injected asmax_tokens. After this change,_should_inject_health_check_max_tokensconsultshealth_check_supports_max_tokens(a separate bool key) first, then the mode allow-list. An operator who relied onhealth_check_max_tokensto bound token usage on a non-chat endpoint that happens to accept the field will silently have it dropped — they now need the additionalhealth_check_supports_max_tokens: truekey. This is a backwards-incompatible behaviour change without a migration notice or a compatibility flag. The test at line 241–250 in the test file explicitly documents this dropped behaviour.Rule Used: What: avoid backwards-incompatible changes without... (source)