chore(deps): bump the dev-dependencies group across 1 directory with 2 updates

[dependabot]

Bumps the dev-dependencies group with 2 updates in the / directory: proptest and criterion.

Updates proptest from 1.7.0 to 1.11.0

Commits

• 7f1367f Merge pull request #641 from proptest-rs/release-1.11
• a63bf7e proptest-state-machine v0.8.0
• d86e9ff add changelog for #640
• 7940313 proptest v1.11.0
• 3ec998c fix #638 changelog
• 8ceb00c Merge pull request #639 from lukoktonos/bits128
• 9c8df1a Merge pull request #638 from folkertdev/f16-support
• ca9d8e1 changelog #638
• a39869f imply f16 feat by unstable
• 85c5ca0 Merge pull request #637 from folkertdev/min-max-assoc-constants
• Additional commits viewable in compare view

Updates criterion from 0.5.1 to 0.6.0

Changelog

Sourced from criterion's changelog.

[0.6.0] - 2025-05-17

Changed

• MSRV bumped to 1.80
• The real_blackbox feature no longer has any impact. Criterion always uses std::hint::black_box() now. Users of criterion::black_box() should switch to std::hint::black_box().
• clap dependency unpinned.

Fixed

• gnuplot version is now correctly detected when using certain Windows binaries/configurations that used to fail

Added

• Async benchmarking with Tokio may be done via a tokio::runtime::Handle, not only a tokio::runtime::Runtime

Commits

• 43bf90a release version 0.6.0 (#860)
• 92696e4 deps: unpin clap (#858)
• 5756a5d chore: bump MSRV to 1.80 (#859)
• 9d887c0 Fixed typo in faq.md (#852)
• 59b791a ci: test against MSRV and 1.87 (#857)
• ace1cc9 Fix warnings from clippy (rust 1.87.0) (#856)
• 7afab6e Commit Cargo.lock to make CI and local debugging more stable (#855)
• 260e2f1 Update Cargo features' comments (#825)
• 58130ff Update to async-std v1.13 (#812)
• d2e705b Add rust-version 1.70 (#813)
• Additional commits viewable in compare view

[github-actions]

🔍 Build Diagnostics Report

Summary

Metric	Base Branch	This PR	Change
Errors	0	0	0
Warnings	5	5	0

🎯 Impact Analysis

Issues in Files You Modified

• 0 new errors introduced by your changes
• 0 new warnings introduced by your changes
• 0 total errors in modified files
• 0 total warnings in modified files
• 0 files you modified

Cascading Issues (Your Changes Breaking Other Files)

• 0 new errors in unchanged files
• 0 new warnings in unchanged files
• 0 unchanged files now affected

Note: "Cascading issues" are errors in files you didn't modify, caused by your changes (e.g., breaking API changes, dependency issues).

✅ No Issues Detected

Perfect! Your changes don't introduce any new errors or warnings, and don't break any existing code.

---

📊 Full diagnostic data available in workflow artifacts

🔧 To reproduce locally:

# Install cargo-kiln
cargo install --path cargo-kiln

# Analyze your changes
cargo-kiln build --output json --filter-severity error
cargo-kiln check --output json --filter-severity warning

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!