build(deps): pin openai==2.33.0 in uv.lock#28088
Merged
mateo-berri merged 1 commit intoMay 16, 2026
Merged
Conversation
openai 2.34.0 began rejecting an explicitly-passed empty-string api_key at client construction (raises OpenAIError before any request), which broke tests/local_testing/test_exceptions.py::test_exception_with_headers and related cases after uv.lock floated openai 2.33.0 -> 2.36.0. Pin back to 2.33.0 (within the existing pyproject >=2.20.0,<3.0.0 range) as a temporary stopgap; longer-term fix to follow.
Contributor
|
No reviewable files after applying ignore patterns. |
ryan-crabbe-berri
approved these changes
May 16, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
fzowl
pushed a commit
to fzowl/litellm
that referenced
this pull request
Jun 24, 2026
openai 2.34.0 began rejecting an explicitly-passed empty-string api_key at client construction (raises OpenAIError before any request), which broke tests/local_testing/test_exceptions.py::test_exception_with_headers and related cases after uv.lock floated openai 2.33.0 -> 2.36.0. Pin back to 2.33.0 (within the existing pyproject >=2.20.0,<3.0.0 range) as a temporary stopgap; longer-term fix to follow.
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
3 participants
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
Pins
openaiback to 2.33.0 inuv.lock(single file, 3 lines: version + sdist hash + wheel hash). Within the existingpyproject.tomlrangeopenai>=2.20.0,<3.0.0— no constraint change.Why
openai2.34.0 began rejecting an explicitly-passed empty-stringapi_keyat client construction —openai.OpenAI(api_key="")now raisesOpenAIErrorbefore any request is made, instead of accepting it and only failing on a real call.tests/local_testing/test_exceptions.py::test_exception_with_headers(andtest_exception_bubbling_up, the Perplexity exception test) deliberately construct the client withapi_key=""because the network call is mocked — the key value was never meant to matter. Whenuv.lockfloatedopenai2.33.0 → 2.36.0 (a side effect of #27557 regenerating the lock; nothing required 2.36), these tests started failing at construction time withMissing credentials ... OPENAI_API_KEY.Resolver dry-run confirmed nothing in the dependency graph needs >2.33 — only the
openailine moved across all 399 packages.Scope / longer-term
Temporary stopgap to unblock CI. The durable fix is a one-line test change (pass a dummy non-empty key, since the request is mocked), which would let the pin be re-relaxed. Tracked for follow-up.
Test plan
uv sync --frozennow installsopenai==2.33.0tests/local_testing/test_exceptions.py::test_exception_with_headersand related cases construct the client and pass without test-code changes