build(deps): update iai-callgrind requirement from 0.12.0 to 0.13.1

[dependabot]

Updates the requirements on iai-callgrind to permit the latest version.

Release notes

Sourced from iai-callgrind's releases.

v0.13.1

[0.13.1] - 2024-08-28

Changed

• Updated locked non-development dependencies:
  • cc: 1.1.13 -> 1.1.15
  • quote: 1.0.36 -> 1.0.37
  • serde: 1.0.208 -> 1.0.209
  • serde_json: 1.0.126 -> 1.0.127
  • syn: 2.0.75 -> 2.0.76

Fixed

• (#248): If the Command's path was a simple command name like echo, cat, the path was interpreted as relative path instead of searched in the $PATH. Relative paths like ./echo are now interpreted as relative to the current directory. If running the Command in a Sandbox, this is the root directory of the Sandbox. Otherwise, it is the directory which is set by cargo bench.

Full Changelog: iai-callgrind/iai-callgrind@v0.13.0...v0.13.1

Changelog

Sourced from iai-callgrind's changelog.

[0.13.1] - 2024-08-28

Changed

• Updated locked non-development dependencies:
  • cc: 1.1.13 -> 1.1.15
  • quote: 1.0.36 -> 1.0.37
  • serde: 1.0.208 -> 1.0.209
  • serde_json: 1.0.126 -> 1.0.127
  • syn: 2.0.75 -> 2.0.76

Fixed

• (#221): If the Command's path was a simple command name like echo, cat, the path was interpreted as relative path instead of searched in the $PATH. Relative paths like ./echo are now interpreted as relative to the current directory. If running the Command in a Sandbox, this is the root directory of the Sandbox. Otherwise, it is the directory which is set by cargo bench.

[0.13.0] - 2024-08-19

!!! IMPORTANT The default to run binary benchmarks in a sandbox has been changed from true to false. The setup and teardown of the binary_benchmark_group! are not executed in the sandbox anymore !!!

The way to set up binary benchmarks has completely changed and has been rewritten from scratch! The api for binary and library benchmarks is now consistent and most features from library benchmarks which were missing for binary benchmarks are now available in binary benchmarks, too. For example comparison of benchmarks by id. If you are using library benchmarks but not binary benchmarks, this release doesn't change much. There are no breaking changes for library benchmarks and you can jump right to the changes section of this release. Otherwise, here's a small introduction to the new api and the changes for binary benchmarks.

There are a lot of advantages for you and honestly for us, too, because we don't have to maintain two completely different apis. Binary benchmarks and library benchmarks can now be written in a similar fashion what makes writing benchmarks for a crate's binaries just easier and faster. No need to learn a completely different api if you already used library benchmarks and vice versa! Also, the feature set between library benchmarks and binary benchmarks diverged over time. For example comparison by id of benchmarks within the same group was available in library benchmarks via the library_benchmark_group! macro but not in binary benchmarks. Such differences are gone, now. Also, if you find out the new #[binary_attribute] does not provide you with the same power as the old builder api, you can still use a low level api and can even intermix the two styles. The new low level api is more intuitive than the old builder api, just more powerful and mirrors the binary_benchmark attribute as much as possible.

... (truncated)

Commits

• 492e1a1 Merge branch 'release'
• e79e7f9 tests(helper): Try another impl of echo helper to fix ci issues
• 61fd5d5 Bump version v0.13.0 -> v0.13.1
• 8b1ffaa chore: Remove README from version bump configuration
• e64ec6b Update CHANGELOG
• 59e91fb Merge pull request #251 from iai-callgrind/renovate/cc-1.x-lockfile
• 960df73 Merge pull request #253 from gamma0987/groups-in-justfile
• 983cc63 chore(just): Group recipes in Justfile. Fix output of command not found
• e10ee57 chore(deps): update rust crate cc to v1.1.15
• 96bcfdc Merge pull request #248 from gamma0987/fix-path
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #456.