Portkey
Log in

Welcome to Portkey Forum

Updated 4 months ago

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

At a glance

The community members are discussing breaking changes in the Portkey API from version 1.1.x to 1.2.x. A community member had issues with the update and had to roll back to version 1.7. The Portkey team acknowledged the issue, stating that it was not a breaking change but rather an issue with the OpenAI SDK. They are working on a permanent fix and asked the community member to share any error messages they encountered. The community members also discussed the previous major update from December last year, which had significant breaking changes that were communicated by the Portkey team.

Useful resources
tthismlguy
·
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
VVrushank | Portkey
That was a big one! Communicated around December last year: https://portkey.ai/docs/changelog/portkeys-december-migration
VVrushank | Portkey
If you are looking to move to the new structure, please let me know and I can share actionable steps directly
VVrushank | Portkey
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.
tthismlguy
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
VVrushank | Portkey
This is for the node SDK?
tthismlguy
python
VVrushank | Portkey
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.
tthismlguy
i didn't get into too much detail
tthismlguy
i had to roll back the library to 1.7 for now
VVrushank | Portkey
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
vvisarg
Hey @thismlguy - Will it be possible to share some error messages that you are getting when you upgrade the package version?
tthismlguy
its been a while, i dont have that error. but 2 of my imports failed
tthismlguy
and i had an issue with processing tool calls
Add a reply
Sign up and join the conversation on Discord