A small release with two fixes to how tak compare renders its report. Both were review findings from #22 that were pushed to that branch after it had already merged, so they shipped in v0.0.4.
Fixed
-
The trend sparkline now agrees with the table beside it.
gather_trendplotted every record's value whilecomparefolds duplicates to the minimum, so a commit carrying several records for one series — a CI re-run, a retry — contributed several points and a noisy re-run put a spike in the sparkline that the table did not show. Trend assembly now takes the minimum per commit, the same rulecompareuses. It also places the compared revision in chronological order when that SHA already appears in the walked history — for exampletak compare v1.33.0 --rev v1.30.0, which compares against an ancestor — instead of appending its value at the end and drawing a line that reads left-to-right but is not in time order. By @jdx in #23. -
The added/removed lists now keep tool identity. Two series differing only by tool rendered identically, so a report could say the same benchmark both started and stopped gating while meaning two different programs. Both lists now name a series by bench, tool (omitted for
self), and runner, matching how the table already names it. By @jdx in #23.
Full Changelog: v0.0.4...v0.0.5