When the Package Manager computes package dependencies, and finds requests for multiple versions of the same package, it automatically selects the package with the fewest dependency levels from the root. In the case of a tie, the Package Manager chooses the highest version among the versions that are tied. It then displays a description of the conflict in the Unity console.
In this example, the higher version (2.0.1) of Package X appears as a dependency three levels away from the project (via Package B and Package C). The Package Manager loads version 2.0.0 of Package X because its dependency is two levels away from the project (via only Package A).
Note: Even if the Package Manager can resolve which package to load, Unity still writes a conflict report to the Unity log file if Unity requests different major versions of the same package, such as 1.0.0 and 2.0.0.