Repository navigation
chore(deps): litellm 1.98.0 -> 1.98.1, so Azure GPT-6 models take reasoning_effort - #5
Merged
johndmendonca merged 1 commit intoSep 25, 2026
Conversation
…soning_effort. - uv.lock: litellm 1.98.0 -> 1.98.1; no other package moves - pyproject.toml unchanged: the litellm>=1.98.0 floor already allows 1.98.1 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
RubenBranco
marked this pull request as ready for review
September 25, 2026 12:32
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.
Why
litellm 1.98.0 recognises only GPT-5 names as Azure reasoning models. For
azure/gpt-6-luna,gpt-6-solandgpt-6-astrait rejectsreasoning_effortwithUnsupportedParamsError. tau2 setslitellm.drop_params = True, so here litellm drops the effort without an error, and GPT-6 runs at its default effort. litellm fixed the name match in BerriAI/litellm#39631 and backported the fix to 1.98.1 (BerriAI/litellm#43130). On 1.98.1, tau2's agent calls, which always carry tools, go to the Azure Responses API withreasoning.effort.1.98.1 is a patch on the 1.98 line. It stays below 1.100, where litellm's hosted_vllm path drops
reasoning_contentfrom tool-loop history.Changes
uv.lockmoves litellm from 1.98.0 to 1.98.1. No other package moves.pyproject.tomlis unchanged, becauselitellm>=1.98.0already allows 1.98.1.Evidence
No model was called. A local stub HTTP server recorded every request litellm sent and returned canned replies.
Tests. 190 passed, 17 failed and 1 xfailed, on main and on this branch. The same 17 tests fail on both with
AuthenticationError: they call a real LLM API, and the run had no provider credentials. The command wasuv run --locked --with pytest --with pytest-asyncio pytest tests. As in #4, it excludedtests/test_domains/test_banking_knowledge,tests/test_gym,tests/test_streamingandtests/test_voice, which need optional dependencies.vLLM requests are unchanged.
LLMAgentonhosted_vllm/glm-5.2-fp8ran a 3-request airline tool loop. The requests were a user turn, the result of aget_user_detailscall from the airline environment, and a second user turn. Every stub reply carriedreasoning_content. The 3 request bodies are byte-identical on 1.98.0 and 1.98.1. The second and third requests replay 1 and 2 assistant messages, each withreasoningandreasoning_content.GPT-6 now gets the effort. Each call used
azure/gpt-6-lunawithreasoning_effort="high"andmax_completion_tokens=16000.LLMAgent, 14 tools/openai/responseswithreasoning.effort: high,max_output_tokens: 16000, modelgpt-6-lunagenerate(), no toolsreasoning_effort: high,max_completion_tokens: 16000generate(), no tools,litellm.drop_params = FalseUnsupportedParamsErrorreasoning_effort: high,max_completion_tokens: 16000Every result above is the same with litellm's live model cost map and with
LITELLM_LOCAL_MODEL_COST_MAP=True.🤖 Generated with Claude Code