build(deps): Bump rand from 0.8.6 to 0.10.1 - #85
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [rand](https://github.com/rust-random/rand) from 0.8.6 to 0.10.1. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](rust-random/rand@0.8.6...0.10.1) --- updated-dependencies: - dependency-name: rand dependency-version: 0.10.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Owner
|
Superseded by #107, which does the same rand 0.8 -> 0.10 bump plus the required SysRng/TryRng API migration in driven-crypto (dependabot's version-only bump cannot compile without it). |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
pmaxhogan
added a commit
that referenced
this pull request
Jul 19, 2026
rand 0.8 -> 0.10 in driven-crypto (the only crate with a direct rand dep). API migration per the rand 0.9/0.10 changelogs: - `use rand::RngCore` -> `use rand::TryRng` (RngCore is a deprecated stub in rand_core 0.10; TryRng is the fallible base trait) - `rand::rngs::OsRng.fill_bytes(buf)` -> `rand::rngs::SysRng.try_fill_bytes(buf).expect(...)` (OsRng was renamed SysRng and re-exported from getrandom 0.4; it only exposes the fallible TryRng surface, and .expect() preserves rand 0.8's behavior of panicking inside OsRng::fill_bytes on entropy failure) Semantics preserved: every call site still fills raw byte buffers straight from the OS CSPRNG (getrandom); no generator, seeding, or distribution changes. chacha20poly1305 0.10 keeps its internal rand_core 0.6 pin via aead 0.5, which is fine - driven-crypto never passes an RNG into an aead API, so the two rand_core majors coexist. Supersedes #85. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014fLmkjpFkiuky72eLBijL4
pmaxhogan
added a commit
that referenced
this pull request
Jul 19, 2026
rand 0.8 -> 0.10 in driven-crypto (the only crate with a direct rand dep). API migration per the rand 0.9/0.10 changelogs: - `use rand::RngCore` -> `use rand::TryRng` (RngCore is a deprecated stub in rand_core 0.10; TryRng is the fallible base trait) - `rand::rngs::OsRng.fill_bytes(buf)` -> `rand::rngs::SysRng.try_fill_bytes(buf).expect(...)` (OsRng was renamed SysRng and re-exported from getrandom 0.4; it only exposes the fallible TryRng surface, and .expect() preserves rand 0.8's behavior of panicking inside OsRng::fill_bytes on entropy failure) Semantics preserved: every call site still fills raw byte buffers straight from the OS CSPRNG (getrandom); no generator, seeding, or distribution changes. chacha20poly1305 0.10 keeps its internal rand_core 0.6 pin via aead 0.5, which is fine - driven-crypto never passes an RNG into an aead API, so the two rand_core majors coexist. Supersedes #85. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014fLmkjpFkiuky72eLBijL4
pmaxhogan
added a commit
that referenced
this pull request
Jul 19, 2026
Bumps `rand` 0.8 -> 0.10 in `driven-crypto` (the only crate with a direct `rand` dependency) and migrates the RNG API accordingly. ## API migration (per rand 0.9/0.10 changelogs) - `use rand::RngCore` -> `use rand::TryRng` (RngCore is a deprecated stub in rand_core 0.10; TryRng is the fallible base trait) - `rand::rngs::OsRng.fill_bytes(buf)` -> `rand::rngs::SysRng.try_fill_bytes(buf).expect(...)` (OsRng was renamed SysRng and re-exported from getrandom 0.4; it only exposes the fallible TryRng surface, and `.expect()` preserves rand 0.8's behavior of panicking inside `OsRng::fill_bytes` on entropy failure) Semantics preserved: every call site still fills raw byte buffers straight from the OS CSPRNG (getrandom); no generator, seeding, or distribution changes. `chacha20poly1305` 0.10 keeps its internal rand_core 0.6 pin via aead 0.5, which is fine - driven-crypto never passes an RNG into an aead API, so the two rand_core majors coexist. ## Verification - `cargo check -p driven-crypto` clean - `cargo test -p driven-crypto` - 41 passed, 0 failed (incl. crypto round-trip + recovery-phrase tests) Supersedes #85 (the plain dependabot lockfile bump, which does not migrate the API and would fail to compile). Close #85 in favor of this. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Bumps rand from 0.8.6 to 0.10.1.
Changelog
Sourced from rand's changelog.
... (truncated)
Commits
27ff4cbPrepare v0.10.1: deprecate featurelog(#1763)98d0638make_rng: document panic and add #[track_caller] (#1761)54e5eaaFix doc error (#1758)1ce4c08Bump itoa from 1.0.17 to 1.0.18 in the all-deps group (#1756)ccb734bdocs: fix typo in doc comment (#1754)357eb7dBump libc from 0.2.182 to 0.2.183 in the all-deps group (#1753)5e77fe5Fix trait references in documentation (#1752)da89185Bump the all-deps group with 3 updates (#1751)50516ffBump the all-deps group with 2 updates (#1749)fd71de9Bump the all-deps group with 2 updates (#1747)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)