semver-compat versions aren't resolved properly for new version

[gnunicorn]

Considering the scenario, which we forget to upgrade a semver compat version update on a sub-dependency, because of caching we don't rebuild the intermediate dependency and that breaks the highest level dependency, if the lowest was released. Experienced here.

Consider this dependencey tree

Super v1.0.0
|- child
  |- dig v1.0.0
| dig v.1.0.1

Because we are building child first, with the released version of dig, when building super, where we pull the new dig, but don't resolve dig again (because we use the cached version), the versions are incompatible.