Repository navigation
deps: crypto-bigint 0.7.6 -> 0.7.9 (0.7.6 to 0.7.8 yanked) - #10
Closed
SovereignTechnology wants to merge 1 commit into
Closed
SovereignTechnology wants to merge 1 commit into
SovereignTechnology wants to merge 1 commit into
Conversation
crates.io yanked crypto-bigint 0.7.6, 0.7.7 and 0.7.8 on 2026-10-25 "due to breaking changes in #1373" (a fix of the blanket Mul impl for NonZero<T>, released as 0.7.9), so cargo deny now fails the check job on a yanked crate. 0.7.9 keeps RUSTSEC-2026-0387's fix (patched >= 0.7.6). Both lockfiles that carried 0.7.6 move; nothing else changes. crypto-bigint is outside the money crates' closure (locked-compiled.txt does not name it), so the lock needs no re-pin.
SovereignTechnology
added a commit
that referenced
this pull request
Oct 26, 2026
crates.io yanked crypto-bigint 0.7.6, 0.7.7 and 0.7.8 on 2026-10-25 "due to breaking changes in #1373" (a fix of the blanket Mul impl for NonZero<T>, released as 0.7.9), so cargo deny now fails the check job on a yanked crate. 0.7.9 keeps RUSTSEC-2026-0387's fix (patched >= 0.7.6). Both lockfiles that carried 0.7.6 move; nothing else changes. crypto-bigint is outside the money crates' closure (locked-compiled.txt does not name it), so the lock needs no re-pin.
Owner
Author
|
Squash-merged as cf9788a |
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.
crates.io yanked crypto-bigint 0.7.6, 0.7.7 and 0.7.8 on 2026-10-25, "due to breaking changes in #1373" (a fix of the blanket
Mulimpl forNonZero<T>, released as 0.7.9).cargo denynow fails the check job witherror[yanked](seen onm2/r32, run 40241168754);mainwould fail the same way on its next run.crates/Cargo.lockandcrates/desktop/Cargo.lock, version and checksum only. The checksum matches the crates.io index.>= 0.7.6).crates/ci/locked-compiled.txtdoes not name it), so the lock needs no re-pin.cargo check -p nfx-proto --locked(k256 → elliptic-curve 0.14 → crypto-bigint) builds with 0.7.9.