[renovate]

This PR contains the following updates:

Package	Update	Change
cargo-codspeed (source)	major	5.0.2 → 6.0.0

---

Release Notes

CodSpeedHQ/codspeed-rust (cargo-codspeed)

v6.0.0

Compare Source

CodSpeed for Rust 6.0.0 removes a source of measurement noise from your CPU Simulation benchmarks, so you can spend less time investigating unexpected changes in unrelated results.

Highlights

Your Divan and Criterion benchmarks now run in separate processes. Changes to one benchmark no longer carry allocator state into the benchmarks that follow it, improving consistency as your benchmark suite evolves.

Early results showed lower run-to-run variance, with roughly 70% fewer benchmarks varying by more than 1%.
No benchmark code changes required. Your WallTime results are unaffected.

Breaking Changes

• Some benchmark values may shift when you upgrade
• Each benchmark adds small process startup overhead to the run

Set CODSPEED_PROCESS_ISOLATION=false to revert to the previous behavior.

What's Changed

• fix(criterion): avoid duplicate setup in simulation iter_batched by @​not-matthias in #​198
• feat(divan): run each benchmark in its own process by @​not-matthias in #​194
• feat(codspeed): declare a Symposium plugin by @​adriencaccia in #​200

Full Changelog: CodSpeedHQ/codspeed-rust@v5.0.3...v6.0.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

[codspeed]

Merging this PR will not alter performance

✅ 2 untouched benchmarks
⏩ 11 skipped benchmarks¹

---

_{Comparing renovate/cargo-codspeed-6.x (580439d) with main (ffab3c6)²}

Footnotes

1. 11 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (4a7e5f6) during the generation of this report, so ffab3c6 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩