chore(deps): bump rand from 0.8.6 to 0.10.1 in the cargo group across 1 directory#422
chore(deps): bump rand from 0.8.6 to 0.10.1 in the cargo group across 1 directory#422dependabot[bot] wants to merge 2 commits into
Conversation
Bumps the cargo group with 1 update in the / directory: [rand](https://github.com/rust-random/rand). Updates `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 dependency-group: cargo ... Signed-off-by: dependabot[bot] <support@github.com>
|
@claude fix builds |
|
Claude finished @mskrzypkows's task in 7m 57s —— View job Fixing builds for rand 0.8 → 0.10 bump
Why I reverted instead of migratingThe dependabot bump from The crypto stack ( Even setting that aside,
RecommendationClose this PR (or
Files touched
|
rand 0.10 brings rand_core 0.10, but the workspace and crypto deps (blst, k256/elliptic_curve) still pin rand_core 0.6. The dual versions mean StdRng (from rand 0.10) no longer satisfies the rand_core 0.6 RngCore/CryptoRng trait bounds in frost, crypto, dkg, breaking the build. rand 0.10 also has many other breaking renames (Rng->RngExt, OsRng->SysRng, SliceRandom->IndexedRandom, removed small_rng feature, removed Clone for StdRng, ...) that would require a coordinated migration across the whole workspace once upstream crypto crates have moved to rand_core 0.10. Co-authored-by: Maciej Skrzypkowski <mskrzypkows@users.noreply.github.com>
|
cannot be updated yet |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the cargo group with 1 update in the / directory: rand.
Updates
randfrom 0.8.6 to 0.10.1Changelog
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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.