MVS requires import path compatibility. For semver-major changes the /v2/-style workaround is OK, except when a package is still v0. What happens in vgo if MY_

MVS requires import path compatibility. For semver-major changes the /v2/-style workaround is OK, except when a package is still v0. What happens in vgo if MY_APP depends on A and B, which both depend on different, incompatible v0 tags of C? I understand that A and B can declare which v0 they want in go.mod, but it can't be solved for MY_APP. This unfortunately isn't hypothetical...