No, I don't think that's true. Consider the following dependency tree, where I am working on
MyPackage, depends on Package A (from: "1.0.0") and Package B (from: "1.0.0")
Package A, depends on Package B (from: "1.0.0")
Imagine that we have the following available versions of each package:
Package A: v1.0.0
Package B: v1.0.0
In this instance, we would have a buildable tree. We'd resolve Package A at v1.0.0 and Package B at v1.0.0.
Now, suppose that Package B releases a v2.0.0. Package B is directly depended upon by me. Package A has not released a new version, and so only has the v1.0.0 release. Should I get a warning here?
While I could raise my own requirement on Package B, to do risks producing an unsatisfiable tree. If I simply do
from: "2.0.0" then I will have unsatisfiable dependences: A requires 1.0.0<2.0.0, and MyPackage requires 2.0.0<3.0.0. The only way I could get this to work is to express my own dependency on B as being 1.0.0<3.0.0, which is unlikely to be acceptable.