Content
@
0 reply
0 recast
0 reaction
Jem
@jem
Is there a clean way to resolve mismatched dependency versions between a parent project and dependencies (via git submodules)? When compiling, `forge` seems to use the parent project's dependencies when compiling a dependency, which often causes problems. e.g. the parent project has a git submodule for OpenZeppelin v4.9.0, but the parent project has a dependency (e.g. G-UNI) that depends on OpenZeppelin v4.1.0. When I build the parent project, it also builds G-UNI, but uses the parent project's OpenZeppelin submodule (v4.9.0), which causes errors. Does Soldeer fix this?
1 reply
0 recast
1 reaction
Almaraz.eth
@alma
Just had this issue yesterday. Was using OZ’s reentrancy guard in the submodule but the parent used a newer version with a different file structure. Downgrading the parent project to match worked but not ideal
0 reply
0 recast
0 reaction
