There are binary incompatibilities between okhttp ...

# squarelibraries

[Aaron Todd]

There are binary incompatibilities between okhttp 4.x and 5.x (e.g. the new Kotlin friendly tag APIs). What is the plan here? I'm assuming binary compatibility isn't a goal? If so can/should okhttp package name change so that 4.x and 5.x can co-exist on the same classpath without resorting to shading?