release: graphn 0.1.5 (relax openai constraint to <3)#11
Merged
Conversation
Customers on openai>=2 hit pip's resolver when installing graphn because pyproject pinned openai<2. The SDK only uses chat.completions.create and models (plus OpenAI / AsyncOpenAI clients and AuthenticationError / InternalServerError exception classes); none of these changed across 1.x -> 2.x. The sole openai 2.0.0 breaking change is in the Responses API (ResponseFunctionToolCallOutputItem.output now allows arrays), which this SDK does not touch. pytest -ra passes 43/43 against openai==2.36.0 with no source changes; ruff is clean.
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
1 participant
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
openairuntime dependency from<2to<3sographninstalls cleanly alongside projects that have already moved toopenai>=2. Several customers have hit pip's resolver on this.0.1.5and add the matching## [0.1.5]CHANGELOG section so the release workflow auto-tags + publishes on merge.Why this is safe
The SDK's only
openaiAPI surface is:OpenAI/AsyncOpenAIclients (constructor args unchanged in 2.x)chat.completions.create(sync + async)models(SyncPage[Model]/AsyncPage[Model])AuthenticationErrorandInternalServerErrorexception classesNone of those changed across the 1.x → 2.x boundary. The only listed
openai2.0.0 breaking change is in the Responses API:ResponseFunctionToolCallOutputItem.outputandResponseCustomToolCallOutput.outputnow accept array forms in addition to strings. This SDK does not import or use the Responses API anywhere.Test plan
ruff check src tests— cleanpytest -ra— 43/43 pass againstopenai==2.36.0(latest at time of writing) with no source changesauto-tagjob createsv0.1.5andpublishships to PyPI in the same workflow runCustomer impact
openai<2keeps working; the lower bound is unchanged at>=1.50.openai>=2can nowpip install graphnwithout resolver conflicts.