When two runs produce different hashes for the same target, the details should help explain what changed. Expand a target in Module Cache or Selective Testing to see its direct target dependencies by name, with links to each module's details. The combined Dependencies hash remains available, so you can spot changes even when the dependency names stay the same.
The destination list now reflects the platforms used to compute the hash. This matters when an external library supports several platforms but a particular project uses only some of them. Details also include embedded-product references, foreign-build inputs, and UI-test device and runtime inputs when reported by the CLI.
Copy as JSON includes the dependency names and individual hash inputs for comparing runs. Inputs that older CLI versions did not report remain unavailable.