Update dependencies and refactor RNG usage to StdRng#10
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #
📑 Description
This PR targets an update of
randto version 0.9.3 to get rid of a (low) CVE report for somerandversions. Additionally, this update also mandates an update ofnum-bigint-digto the latest version.Although rand v0.9.3 still exposes OsRng, we move away from it in this PR and use StdRng instead. We do this, in order to simplify future version updates of the rand abd num-bigint-dig crates. In particular, num-bigint-dig does not yet use the newly introduced
RngExttrait by the rand crate, which blocks updating to rand 0.10.1 directly.✅ Checks
ℹ Additional Information