Update Rust crate codspeed-criterion-compat to v5

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
codspeed-criterion-compat (source)	workspace.dependencies	major	4.4.1 → 5.0.0	5.0.1

---

Release Notes

CodSpeedHQ/codspeed-rust (codspeed-criterion-compat)

v5.0.0

Compare Source

💥 BREAKING

MSRV bumped to 1.85 for all packages: codspeed, codspeed-criterion-compat, codspeed-divan-compat

What's Changed

This release includes a fix for benchmark URI generation when users do not use the provided macros to declare their criterion main function.

• fix(criterion-compat): fix URI formatting when criterion_group!/criterion_main! are bypassed by @​not-matthias in #​169
• Fix lower bound of cc crate by @​konstin in #​182
• Update colored dep by @​rukai in #​142
• update getrandom to 0.4 by @​Ludea in #​177

New Contributors

• @​rukai made their first contribution in #​142
• @​Ludea made their first contribution in #​177

Full Changelog: CodSpeedHQ/codspeed-rust@v4.7.0...v5.0.0

v4.7.0

Compare Source

What's Changed

Manual sampling for criterion

Note: ignored under CodSpeed simulation mode (single measured iteration). Only takes effect in walltime mode.

We introduced a new finer control way of defining a criterion benchmark to have full control over how many times your code is ran.
This bypasses criterion's original sampler, which we still recommend using if you do not have specific control needs.

use codspeed_criterion_compat::{criterion_group, criterion_main, Criterion, IterManualOptions};

fn bench_my_function(c: &mut Criterion) {
    c.bench_function("my_function", |b| {
        b.iter_manual_unstable(
            IterManualOptions::new()
                .rounds(5)   // 5 measurement samples, can be lower than criterion's imposed 10
                .iters(1000)  // 1000 calls per sample
                .warmup(5),   // 5 unmeasured warmup iterations
            || my_function(),
        );
    });
}

criterion_group!(benches, bench_my_function);
criterion_main!(benches);

Please note that this API is still under development and may change with future releases.

• fix(cargo-codspeed): forward args after -- to bench binaries by @​not-matthias in #​179
• chore: bump instrument-hooks by @​not-matthias in #​178
• feat(criterion-compat): add iter_manual to have finer control over the iteration loop by @​GuillaumeLagrange in #​180

Full Changelog: CodSpeedHQ/codspeed-rust@v4.6.0...v4.7.0

v4.6.0

Compare Source

What's Changed

This release adds first support for macOS walltime.

Please note that profiling and other instruments are not yet available on macOS and will come in a later update.

• Support macos walltime without profiling in codspeed-rust by @​GuillaumeLagrange in #​176

Full Changelog: CodSpeedHQ/codspeed-rust@v4.5.0...v4.6.0

v4.5.0

Compare Source

What's Changed

We now collect buildtime and runtime environment data to warn users about differences in their runtime environment when comparing two runs against one another.

This data includes toolchain metadata like version and build options, as well as a list of dynamically loaded linked libraries.

• feat(codspeed): collect Rust toolchain environment at build time by @​GuillaumeLagrange in #​171
• Bump instrument hooks and collect linked libraries by @​GuillaumeLagrange in #​173

Full Changelog: CodSpeedHQ/codspeed-rust@v4.4.1...v4.5.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 4am on Wednesday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.toml

Artifact update for codspeed-criterion-compat resolved to version 5.0.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 5.0.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/