@cod10129 describes the actual problem accurately; it’s not really cargo’s fault that things get worse[1]. This problem could only be fixed either by nuid maintainers releasing point releases for 0.3.* (and probably also 0.4.*) that fix the incorrect rand dependency specifications, or by the crate bringing in this dependency (nats) updating their dependency to nuid version 0.5 [unless that’s a public dependency], which is unlikely judging by the maintenance message suggesting transition to async-nats which does depend on the nuid version 0.5 but has a different API presumably (at least in that it involves async fn) 
though the rustc error could probably consider mentioning commands such as
cargo update timedirectly. Maybe something likecargo update time@0.3works, too, but ensures even more minimal changes? [I’m not 100% sure if cutting off the version here is supported or if you need the exacttime@0.3.…something…here] ↩︎