chore(deps): bump websocksets to 15+

[0xRAG]

What was wrong?

OpenAI Agents released voice support, but it requires websockets 15+. In AgentKit we use web3.py extensively in our core package. We would like to support OpenAI's voice-enabled agents which is possible only through upgrading web3.py's dependency on websockets.

Related to and closes #3641

How was it fixed?

There are some breaking changes in between websockets 13 and 15, however there are access points for newly deprecated methods and fields. I'm sure the web3.py library would like to take advantage of the improvements to websockets (there is a full upgrade guide here), but for the (admittedly selfish) scope of combining web3.py & AgentKit & OpenAI Agents, this PR should suffice, while being directionally correct.

I tested the changes by installing the latest websockets and running the full test suite via make test. The test results are exactly the same as on main.

References

• websocket 14.0 backwards-incompatible changes
• websocket 15.0 backwards-incompatible changes
• websocket asyncio upgrade guide

Todo:

• Clean up commit history
• Add or update documentation related to these changes
• Add entry to the release notes

Cute Animal Picture

[fselmo]

Thanks @0xRAG. We've discussed this and I think for the purposes of not breaking, we should keep python 3.8 support and remain on a v7 minor release path.

I realized that all breaking changes happen under the _ws private underlying API. So technically we can add a python version check via compat, as I did here, and what actually "breaks" doesn't really break because it was already considered an internal / breakable, non-public, API.

I am going to cherry-pick some of those commits here if you don't mind and we can take a last look together and see if this checks all the boxes.

cc: any and all in #3641

[0xRAG]

Sounds good thanks @fselmo!

[fselmo]

Looks like websockets did a great job backporting these changes. All that was needed in the end was importing from websockets.legacy paths and this is already version agnostic. For now, this is a nice easy change that doesn't break anything. We'll be able to dig in a bit more into new websockets features as a separate scope.

@0xRAG does this work as a first step toward compatibility with no breaking changes 👀 ?

[0xRAG]

Amazing! Yes, bumping the upper range to include up to websockets 16 should unblock us. Thanks @fselmo! When can we expect this to land in a release?

[fselmo]

Amazing! Yes, bumping the upper range to include up to websockets 16 should unblock us. Thanks @fselmo! When can we expect this to land in a release?

It's too late in the day today so I'll try to get a release out as quickly as tomorrow :)

[0xRAG]

Sounds good!

[fselmo]

@0xRAG web3.py 7.10.0 was just released with this change!

[0xRAG]

Amazing, thanks @fselmo!

[0xRAG]

Confirmed this unblocked us @fselmo! If you're curious, here's a PR in AgentKit bumping web3.py and adding support for the OpenAI voice agent coinbase/agentkit#620

[fselmo]

Happy to hear it @0xRAG! Thanks for sharing and glad to have unblocked everyone dependent on this. I think this was a very good example of how to break things by websockets. Quite an elegant and easy path for everyone in the end.