Skip to content

Bump num-bigint from 0.4.8 to 0.5.1 - #525

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/num-bigint-0.5.1
Open

Bump num-bigint from 0.4.8 to 0.5.1#525
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/num-bigint-0.5.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 14, 2026

Copy link
Copy Markdown
Contributor

Bumps num-bigint from 0.4.8 to 0.5.1.

Changelog

Sourced from num-bigint's changelog.

Release 0.5.1 (2026-07-04)

Contributors: @​cuviper

Release 0.5.0 (2026-07-02)

  • Upgrade to rand v0.10 and/or v0.9, and split rand_core.
    • The former rand feature is now split into multiple features, rand_0_9, rand_core_0_9, rand_0_10, and rand_core_0_10, depending on the version and feature set you need.
    • The RandBigInt extension trait is now split into BigRng09 and BigRng010 for each version.
    • The gen_* methods are deprecated in favor of new random_* methods.
    • This is also a value-breaking release, as rand defines it.

Contributors: @​bionicles, @​cuviper, @​divergentdave

Commits
  • 33c59ba Merge pull request #348 from cuviper/bz-alg2-step3b
  • 38b68f6 Release 0.5.1
  • f4a43f5 Fix the missing part of the Burnikel-Ziegler algorithm
  • ebfd89a Add failing tests for a bug in B-Z division
  • 0ab95df Merge pull request #338 from cuviper/rand-0.10
  • 33d6998 Release 0.5.0
  • 84d05b7 Clean up manifests of ci crates
  • f8daf56 Allow clippy::duplicate_mod where intended
  • 022310a Rearrange the rand features to support both 0.9 and 0.10
  • 537a036 ci: use the fallback resolver for deps
  • Additional commits viewable in compare view


Note

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-bigint dependency from 0.4.8 to 0.5.1 in Cargo.toml (still with the serde feature), with matching Cargo.lock updates.

The lockfile now pins num-bigint 0.5.1 for this crate while other packages in the graph continue to use 0.4.8 via num / 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.

@dependabot dependabot Bot added Changed Required label for PR that categorizes merge commit message as "Changed" for changelog dependencies Pull requests that update a dependency file rust Pull requests that update Rust code labels Jul 14, 2026
@socket-security

socket-security Bot commented Jul 14, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedcargo/​num-bigint@​0.5.110010093100100

View full report

@dependabot dependabot Bot changed the title Bump num-bigint from 0.4.6 to 0.5.1 Bump num-bigint from 0.4.8 to 0.5.1 Jul 28, 2026
@dependabot
dependabot Bot force-pushed the dependabot/cargo/num-bigint-0.5.1 branch from 55a584b to 0ede698 Compare July 28, 2026 02:08
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
dependabot Bot force-pushed the dependabot/cargo/num-bigint-0.5.1 branch from 0ede698 to 53be7df Compare August 7, 2026 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Changed Required label for PR that categorizes merge commit message as "Changed" for changelog dependencies Pull requests that update a dependency file rust Pull requests that update Rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants