Bump num-bigint from 0.4.8 to 0.5.1 - #525
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
dependabot
Bot
force-pushed
the
dependabot/cargo/num-bigint-0.5.1
branch
from
July 28, 2026 02:08
55a584b to
0ede698
Compare
Bumps [num-bigint](https://github.com/rust-num/num-bigint) from 0.4.8 to 0.5.1. - [Changelog](https://github.com/rust-num/num-bigint/blob/main/RELEASES.md) - [Commits](rust-num/num-bigint@num-bigint-0.4.8...num-bigint-0.5.1) --- updated-dependencies: - dependency-name: num-bigint dependency-version: 0.5.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/num-bigint-0.5.1
branch
from
August 7, 2026 17:03
0ede698 to
53be7df
Compare
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.
Bumps num-bigint from 0.4.8 to 0.5.1.
Changelog
Sourced from num-bigint's changelog.
Commits
33c59baMerge pull request #348 from cuviper/bz-alg2-step3b38b68f6Release 0.5.1f4a43f5Fix the missing part of the Burnikel-Ziegler algorithmebfd89aAdd failing tests for a bug in B-Z division0ab95dfMerge pull request #338 from cuviper/rand-0.1033d6998Release 0.5.084d05b7Clean up manifests of ci cratesf8daf56Allowclippy::duplicate_modwhere intended022310aRearrange therandfeatures to support both 0.9 and 0.10537a036ci: use the fallback resolver for depsNote
Low Risk
Dependency-only bump with no application code changes; the upgrade includes a bigint division fix and keeps serde serialization behavior via the same feature flag.
Overview
Bumps the direct
num-bigintdependency from 0.4.8 to 0.5.1 inCargo.toml(still with theserdefeature), with matchingCargo.lockupdates.The lockfile now pins
num-bigint 0.5.1for this crate while other packages in the graph continue to use0.4.8vianum/clvmr. No Rust source changes—existing uses (e.g.ToBigInt) stay on the same API surface.Reviewed by Cursor Bugbot for commit 53be7df. Bugbot is set up for automated code reviews on this repo. Configure here.