I just did a preliminary analysis of the reverse dependencies and it's looking pretty good. (details below). Though I would like to wait until I have confirmation that rust-selectors has migrated to testing.
Matthias, would you object to me updating rust-ruma-common to 0.11.x as part of this update? rust-chrono-tz - fixed upstream in 0.6.3 (and also higher semver-breaking versions) rust-chrono-tz-build - fixed upstream in 0.0.3 (and other higher versions but this is the one needed for chrono-tz) rust-coreutils - no change needed, dependency already allows 0.11 and upstream already uses 0.11 rust-cssparser - no change needed, dependency already allows 0.11 and upstream already uses 0.11 rust-markup5ever - cargo test --all --all-targets --all-features passes after dependency bump. rust-phf-codegen - presumablly meant to be upgraded in lockstep with phf rust-phf-generator - presumablly meant to be upgraded in lockstep with phf rust-phf-macros - presumablly meant to be upgraded in lockstep with phf rust-phf-shared - presumablly meant to be upgraded in lockstep with phf rust-rust-code-analysis - already broken and not in testing rust-selectors - RUSTC_BOOTSTRAP=1 cargo test --all --all-targets --all-features passes after dependency bump, currently undergoing it's own semver transition rust-string-cache - cargo test --all --all-targets --all-features passes after dependency bump. rust-string-cache-codegen - cargo test --all --all-targets --all-features passes after dependency bump. rust-tls-parser - RUSTC_BOOTSTRAP=1 cargo test --all --all-targets --all-features passes after dependency bump and some fixes for unrelated issues. rust-tokio-postgres - dependency patch needs dropping. rust-ruma-common - fixed upstream in 0.11.3 (which is semver-breaking but there are no rdeps, I asked count_omega on irc if updating was reasonable, if not then I suspect patching will also be an options)
