title: Why is the latest possible version not being installed in CI with caret versioning
body: <p>I have some nested dependencies that use caret versioning e.g. <code>&quot;lodash&quot; :&quot;^4.2.0&quot;</code>.</p>
  <p>Why is it that when I install packages from a fresh clone, I don't get the latest version that supports that versioning? Currently that would be - <code>4.17.21</code>. I could understand if my other packages need a lower version of lodash but they also have something similar with caret versions.</p>
  <p>For some reason <code>4.17.20</code> is being installed by yarn. Something is telling my yarn lockfile to resolve to <code>4.17.20</code>. The only way I can get around this is to use resolutions in my <code>package.json</code> however this is occurring for many packages and I don't want to do this if possible. Is there something I'm missing that is causing versions to be resolved in the lockfile?</p>