Upgrade from getrandom 0.2 to getrandom 0.4.2, bumping MSRV to 1.85.#2756
Upgrade from getrandom 0.2 to getrandom 0.4.2, bumping MSRV to 1.85.#2756briansmith merged 2 commits intomainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2756 +/- ##
==========================================
- Coverage 96.69% 96.68% -0.02%
==========================================
Files 204 204
Lines 20388 20392 +4
Branches 519 519
==========================================
Hits 19715 19715
- Misses 557 561 +4
Partials 116 116 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
fe86f46 to
dc5efe7
Compare
|
Rust 2024 changes will be done in a separate PR. |
|
The "1.85" MSRV tests in CI need to be updated to use the MSRV-aware resolver, I guess, as otherwise an indirect downstream dependency requires 1.87. |
affe555 to
5bf9369
Compare
8807d93 to
9eb10d5
Compare
|
I updated this substantially, especially to require getrandom 0.4.2+ and to improve the CI. |
9eb10d5 to
004124a
Compare
|
rust-random/getrandom#824 reduces the MSRV of |
004124a to
984c6a9
Compare
d94f048 to
82740f4
Compare
|
See also rust-random/getrandom#827 for reducing the dependencies of getrandom (and the MSRV issues) for wasip2/wasip3 targets. |
68140bd to
f51163d
Compare
a04e3b2 to
6412d21
Compare
6412d21 to
e49ab05
Compare
… to 1.85. getrandom 0.4.2 seems to have implemented good enough support with its wasm_js feature to make it usable as an alternative to getrandom 0.2. Rust 1.84 (and getrandom 0.3) dropped support for the old wasm32-wasi target, and won't build for that target, so stop testing it.
e49ab05 to
2f04962
Compare
getrandom 0.4.2 seems to have implemented good enough support with its wasm_js feature to make it usable as an alternative to getrandom 0.2.
Rust 1.84 (and getrandom 0.3) dropped support for the old wasm32-wasi target, and won't build for that target, so stop testing it.