chore(deps): bump rand_core to 0.10.0-rc-5#108
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #108 +/- ##
==========================================
- Coverage 97.93% 97.93% -0.01%
==========================================
Files 14 14
Lines 1893 1891 -2
==========================================
- Hits 1854 1852 -2
Misses 39 39 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Note: I'll have a |
d7ce29a to
047afeb
Compare
|
I don't know if we need a bump of |
|
I'm maybe a half hour away. I think it's good if the versions are in lockstep. There hopefully aren't any breaking changes but it'd be good to know for sure. |
|
It's out: https://crates.io/crates/crypto-bigint/0.7.0-rc.19 Hopefully doesn't break anything but it'd be good to know and get included along with bumping everything else. I can try it out on your branch if you want. (I can look in a bit, seems it broke something in |
|
Ugh, ran into some breakages in |
|
There is some amount of breakage in |
ha. |
|
|
047afeb to
f1a4df5
Compare
|
For some reason it would not find the |
|
@baloo this release added an overlapping impl: Maybe we should remove the |
68aec46 to
266af98
Compare
rand_core to 0.10.0-rc-4rand_core to 0.10.0-rc-5
266af98 to
c9428e3
Compare
c9428e3 to
bf0cecb
Compare
|
@fjarri can you take a look at this one? Unfortunately it's more breaking changes that block upgrading everything else |
7e75f6e to
0101887
Compare
| harness = false | ||
|
|
||
| [patch.crates-io] | ||
| rand = { git = "https://github.com/rust-random/rand.git" } |
There was a problem hiding this comment.
Sadly yes. This is only used to run tests though. There was some amount of API breakage between rand_core rc-3 and rc-5.
There was a problem hiding this comment.
Yeah, there hasn't been a new rand release yet. But, since it's a dev-dependency, it won't block publishing a new prerelease
There was a problem hiding this comment.
Could you pin the revision, just so that it doesn't break stuff in future runs?
There was a problem hiding this comment.
Sidebar: that's what Cargo.lock is for! 😜
There was a problem hiding this comment.
I admit I am not entirely sure if it bumps the revision automatically when the new one is available.
There was a problem hiding this comment.
I don't believe any dependency management robot supports that.
|
Do you need a new release with this? |
|
Yes that'd be great, thanks! |
* chore(deps): bump `rand_core` to `0.10.0-rc-5` * chore(deps): bump `crypto-bigint` to `0.7.0-pre.21`
Depends: