v0.30.x CI

[speedstyle]

v0.30.x/.github/workflows/ci.yml#L110 would need a lot more dependencies locked for 1.70 MSRV.

cargo generate-lockfile
cargo update -p softbuffer --precise 0.4.6
cargo update -p image --precise 0.25.6
cargo update -p unicode-ident --precise 1.0.22
cargo update -p syn --precise 2.0.114
cargo update -p quote --precise 1.0.44
cargo update -p log --precise 0.4.29

cargo update -p wayland-protocols-plasma --precise 0.3.10
cargo update -p wayland-protocols-wlr --precise 0.3.10
cargo update -p wayland-protocols --precise 0.32.10
cargo update -p wayland-cursor --precise 0.31.12
cargo update -p wayland-client --precise 0.31.12
cargo update -p wayland-scanner --precise 0.31.8
cargo update -p wayland-backend --precise 0.3.12
cargo update -p wayland-sys --precise 0.31.8
cargo update -p crossfont --precise 0.8.0

cargo update -p libloading --precise 0.8.8
cargo update -p gethostname --precise 1.0.2

cargo update -p orbclient --precise 0.3.51
cargo update -p libredox --precise 0.1.6
cargo update -p redox_syscall@0.5.18 --precise 0.5.2

cargo update -p objc2-encode --precise 4.0.3

cargo update -p unicode-segmentation --precise 1.12.0
cargo update -p polling --precise 3.10.0
cargo update -p windows-sys@0.61.2 --precise 0.60.2

cargo update -p android-activity --precise 0.6.0
cargo update -p jni-sys@0.3.1 --precise 0.3.0
cargo update -p proc-macro-crate --precise 3.4.0
cargo update -p toml_edit --precise 0.23.5
cargo update -p toml_datetime --precise 0.7.1
cargo update -p toml_parser --precise 1.0.2
cargo update -p indexmap --precise 2.11.4

I was going to PR, but some of them fail! Exact-version dependencies of web-sys and wasm-bindgen-futures on js-sys and wasm-bindgen make it harder to resolve with individual updates.

cargo update -p bumpalo --precise 3.14.0
cargo update -p pin-project --precise 1.1.10
cargo update -p js-sys --precise 0.3.82
cargo update -p web-sys --precise 0.3.82
cargo update -p wasm-bindgen --precise 0.2.105
cargo update -p wasm-bindgen-futures --precise 0.4.55

The duplicates could also fail easily if they release eg windows-sys@0.61.3. It might be better to use a newer rust-version-aware cargo to generate the lockfile, then build with MSRV toolchain – that's how I found most of these. Or bump the version for future 0.30.x patches.

I'm not sure if this was a drag on backports like #4580 (that kde 'regression' brought me here), or how much more will be backported before/after a 0.31 release, but if it helps