chore(deps): update rust crate codspeed-criterion-compat to v2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
codspeed-criterion-compat (source)	dev-dependencies	major	1.1.0 -> 2.2.0

---

Release Notes

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

v2.2.0

Compare Source

What's Changed

It's now possible to disable codspeed_criterion_compat default features.

Details

• fix: allow disabling criterion default features by @​art049 in https://github.com/CodSpeedHQ/codspeed-rust/pull/12

Full Changelog: CodSpeedHQ/codspeed-rust@v2.1.0...v2.2.0

v2.1.0

Compare Source

🎉 What's Changed

• Relative paths are now properly handled when using the working-directory action parameter.

📚 Details

• fix: fix relative path when using working-directory by @​art049 in https://github.com/CodSpeedHQ/codspeed-rust/pull/9

Full Changelog: CodSpeedHQ/codspeed-rust@v2.0.0...v2.1.0

v2.0.0

Compare Source

🎉 What's Changed

• Each benchmark is warmed up before each run to reduce the flakiness and the side effects related to the order in which the benchmarks are run.
• AsyncBencher is now supported with the criterion compatibility layer.
• Debug symbols are now generated during the build of the benchmarks, allowing more granularity in the performance reports and detailed profiling. More details can be found in the documentation.

🚀 Migration Path

This is a breaking change and might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🎉!

In some cases, the warmup might optimize out the benchmark. In that case, adding black_box should help, also don't hesitate to open an issue so we can have a look and document the behavior.

We recommend you create a standalone PR to update the package, acknowledge the potential regressions, and merge it to update the baseline on your default branch.

📚 Details

Features

• feat: add debug symbols in the benchmark build config by @​art049 in https://github.com/CodSpeedHQ/codspeed-rust/pull/4
• feat: add AsyncBencher support by @​art049 in https://github.com/CodSpeedHQ/codspeed-rust/pull/7
• feat!: add warmup runs by @​art049 in https://github.com/CodSpeedHQ/codspeed-rust/pull/5

Internals

• chore: bump criterion by @​art049 in https://github.com/CodSpeedHQ/codspeed-rust/pull/8

Full Changelog: CodSpeedHQ/codspeed-rust@v1.1.0...v2.0.0

---

Configuration

📅 Schedule: 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 has been generated by Mend Renovate. View repository job log here.

[codspeed-hq]

CodSpeed Performance Report

Merging #451 will degrade performances by 24.74%

_{Comparing renovate/codspeed-criterion-compat-2.x (9fcf314) with main (7dc788e)}

🎉 Hooray! codspeed-rust just leveled up to 2.2.0!

A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🥳!
Curious about what's new? Visit our releases page to delve into all the awesome details about this new version.

Summary

⚡ 3 improvements
❌ 2 regressions
✅ 27 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	renovate/codspeed-criterion-compat-2.x	Change
⚡	fill-corner_to_corner_bfs	6.5 ms	5.6 ms	+15.6%
❌	fill-corner_to_corner_astar	546.9 µs	639.7 µs	-14.49%
⚡	fill-no_path_astar	8.3 ms	7 ms	+18.75%
⚡	fill-no_path_bfs	6.8 ms	5.6 ms	+20.89%
❌	fill-corner_to_corner_fringe	499.7 µs	664 µs	-24.74%

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.