I’ve searched around for answers to this and so far come up short.
I have an integration that I wrote and use for myself, which necessarily depends on a particular external python library. That external library has its own dependencies, which include protobuf, in that library currently pinned to version 5.29.2.
When homeassistant updates, it occasionally also bumps its internal version of protobuf. If that version exceeds the version in the library, then the integration fails to load, because it is requesting a lower version number than installed.
This seems like this should be something easily solvable where a custom component integration should get its own venv and not be required to have the same versions of packages as are installed systemwide on HAOS, but that doesn’t seem to be the case.
There must be some way to solve this cleanly, or else I imagine integrations would be constantly breaking all over the place; but I cannot seem to find what it is. Any help would be appreciated.