v4.0.0

Caution

BREAKING CHANGES
Starting in this release, checksum.json now records the haddock3 version used at the start of a benchmark, and validates it hasn't changed mid-run (#196).

Impact: checksum.json files created by v3.2.0 or earlier do not contain this field. If you resume a benchmark that was started on an older version, haddock-runner will fail to parse the existing checksum file with an error like:

Failed to parse checksum file

What to do:

• Finish it on the old binary before upgrading, or
• Delete/regenerate checksum.json and start a fresh run on the new version (note: this resets file-change tracking for that run).
• New benchmarks started on this version are unaffected.

What's Changed

• catch haddock3 version drift by @rvhonorato in #196
• add summary module by @rvhonorato in #197

Full Changelog: v3.2.1...v4.0.0