Question about okhttps bom. It seems like all of o...
# squarelibrariesc
Colton Idle
10/09/2025, 10:16 PMQuestion about okhttps bom. It seems like all of okhttps artifacts are versioned together in lock step. why the bom? from what i can tell, bom seems to be more helpful in situations where artifact versions are all scattered?
e
ephemient
10/09/2025, 10:25 PMusing a bom helps avoid cases where, due to transitive dependencies, you end up with different versions of different parts of the library (which will lead to broken okhttp)
today i learned 1
➕ 2
j
jw
10/09/2025, 10:39 PMWe should be using constraints
➕ 1
jw
10/09/2025, 10:40 PMThey're automatic, the BOM is opt in and awkward
e
ephemient
10/09/2025, 10:41 PMyeah, if you did that upstream then it would solve the issue for all consumers
c
Colton Idle
10/10/2025, 2:50 AMoooh true. didn't think about that ephemient. and yeah i suppose constraints would be a nice path forward!
s
Stylianos Gakis
10/10/2025, 1:17 PMColton can probably subscribe to https://github.com/square/okhttp/issues/9084 I would suspect any updates on this would be mentioned there
👌 1