chore(deps): bump num-bigint from 0.4.8 to 0.5.1 - #828
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
dependabot
Bot
requested review from
0xForerunner,
0xOsiris,
Dzejkop and
Kemperino
as code owners
July 9, 2026 00:01
dependabot
Bot
requested review from
karankurbur,
kilianglas and
murph
as code owners
July 9, 2026 00:01
dependabot
Bot
requested review from
alessandromazza98,
cichaczem and
piohei
as code owners
July 9, 2026 00:01
0xOsiris
approved these changes
Jul 9, 2026
dependabot
Bot
force-pushed
the
dependabot/cargo/num-bigint-0.5.1
branch
from
August 6, 2026 13:56
e0c6a56 to
4733f59
Compare
Contributor
Benchmark ResultsBase and PR measured on the same runner in the same workflow run.
Raw
|
Contributor
Author
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
dependabot
Bot
force-pushed
the
dependabot/cargo/num-bigint-0.5.1
branch
from
August 7, 2026 13:17
4733f59 to
32665d0
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 15:22
32665d0 to
eabcd4e
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
Scope is a single transitive dependency version bump with no source edits; main caveat is upstream bigint division fixes in 0.5.x affecting cryptographic big-integer paths in attestation hints.
Overview
Bumps
num-bigintonworld-chain-proof-nitro-enclavefrom 0.4 to 0.5 and refreshesCargo.lockso that crate resolves to 0.5.1 instead of 0.4.8.There are no application code changes; the dependency still backs P-384 hint math in
p384_hints.rs(BigUint/BigInt). The 0.5 line drops the defaultrand0.8 edge from this crate’s lock entry, which matches use that does not enablenum-bigint’s randomness features.Reviewed by Cursor Bugbot for commit eabcd4e. Bugbot is set up for automated code reviews on this repo. Configure here.