> Instead of trying to get the latest version it's going to try to get the oldest. No, minimal refers to the number of dependency changes between upgrades, not

> Instead of trying to get the latest version it's going to try to get the oldest. No, minimal refers to the number of dependency changes between upgrades, not the version numbers of the dependencies. Dependency conflicts initially resolve to the higher of the two versions. https://research.swtch.com/vgo-mvs https://research.swtch.com/vgo-mvs section " Algorithm 1: Construct Build List" In the example, a dependency is upgraded and no longer needs one of the shared transient dependencies. Instead of downgrading it to the version declared by the unchanged dependency, it keeps the higher version that you were already using. When upgrading, transient dependencies are never downgraded, only added (or removed). https://research.swtch.com/vgo-mvs https://research.swtch.com/vgo-mvs section " Algorithm 3. Upgrade One Module"