v2.1.0

🎉 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 #9

Full Changelog: v2.0.0...v2.1.0

v2.0.0

🎉 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 #4
• feat: add AsyncBencher support by @art049 in #7
• feat!: add warmup runs by @art049 in #5

Internals

• chore: bump criterion by @art049 in #8

Full Changelog: v1.1.0...v2.0.0

v1.1.0

What's Changed

cargo-codspeed

• Support the --features build flag by @art049 in #2

Full Changelog: v1.0.0...v1.1.0

v1.0.1

Full Changelog: v1.0.0...v1.0.1

v1.0.0

Initial release

Full Changelog: https://github.com/CodSpeedHQ/codspeed-rust/commits/v1.0.0