Welcome to Portkey Forum

Updated 3 weeks ago

The Portkey API 1.1.x -> 1.2.x Had a Bunch of Breaking Changes, Do You Guys Share Breaking Changes Somewhere?

the portkey api 1.1.x -> 1.2.x had a bunch of breaking changes, do you guys share breaking changes somewhere?
V
t
v
13 comments
If you are looking to move to the new structure, please let me know and I can share actionable steps directly
Please also note, we have not deprecated the old APIs yet, and they will keep functioning as it is. We plan to sunset them later this quarter.
hmm not sure if we're talking about the same update. i'm talking about a minor update from 1.1 to 1.2. i installed fisrt a months or so ago and updated again this week
This is for the node SDK?
This was not a breaking change. We went from v1.1.7 to v1.2.0, where we introduced OpenAI SDK wrapper for our SDK.

OpenAI has recently removed some beta methods from their SDK (like assistants.file), which may have caused Python dependency conflicts if your OpenAI package is updated to latest.

Confirming that this is an issue and we're working on it.

Please let me know if you think something else is happening though.
i didn't get into too much detail
i had to roll back the library to 1.7 for now
Cool! We're thinking of a permanent fix for this - will let you know here. Please do check the OpenAI SDK version once - it may be latest and thus causing issue
Hey @thismlguy - Will it be possible to share some error messages that you are getting when you upgrade the package version?
its been a while, i dont have that error. but 2 of my imports failed
and i had an issue with processing tool calls
Add a reply
Sign up and join the conversation on Discord