fix(deps): raise rustfft and rand version floors - #309
Conversation
Signed-off-by: Bhavya Jain <jainbhavya0810@gmail.com>
PR Check Summary
CI will run: build, test, clippy, fmt, cargo-deny, DCO, semver. |
|
Warning Review limit reached
Next review available in: 17 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
rustfftversion from6to6.4.1.randversion from0.9to0.9.4.small_rngfeature.Cargo.toml.Why
The existing Cargo requirements use compatible version ranges:
rustfft = "6"allows compatible6.xreleases.rand = "0.9"allows compatible0.9.xreleases.Although
Cargo.lockalready resolvesrustfft 6.4.1andrand 0.9.4, the manifest still permits resolution to older compatible versions.Raising the version floors ensures that dependency resolution cannot fall below the currently validated releases while still allowing future semver-compatible updates.
Closes #273
How
rustfftto6.4.1.randto0.9.4.Cargo.lockrequires no change because it already resolves both requested versions.upstream/main.The following checks passed:
cargo metadata --locked --format-version 1cargo fmt --all -- --checkcargo clippy --locked --workspace --all-targets --all-features -- -D warningscargo test --locked --workspace --all-featuresRUSTDOCFLAGS="-D warnings" cargo doc --locked --workspace --no-deps --all-featurescargo bench --locked --workspace --no-run --all-featurescargo machetegit diff --checkcargo deny checkcurrently fails on the existingupstream/mainlockfile because of these pre-existing advisories:RUSTSEC-2026-0204forcrossbeam-epoch 0.9.18RUSTSEC-2026-0186formemmap2 0.9.10This PR does not modify
Cargo.lockor either affected dependency.Checklist
cargo test --workspacepassescargo clippy --workspace -- -D warningspassescargo fmt --allappliedCHANGELOG.mdupdated (not required; this is not a user-facing change)