v5.1.1

[5.1.1] - 2026-06-28

Bug Fixes

• fix(bench): measure native-binary size from the published npm artifact (#150)

v5.1.0

[5.1.0] - 2026-06-17

Features

• feat(bench): pin ferrflow to single thread + report parallel stat with runner cores (#145)

v5.0.6

[5.0.6] - 2026-06-15

Bug Fixes

• fix(run): push tags to dummy remote so semantic-release stops failing (#141)

v5.0.5

[5.0.5] - 2026-06-15

Bug Fixes

• perf(bench): lower default warmup from 3 to 2 (~10% wall-time saving) (#140)

v5.0.4

[5.0.4] - 2026-06-15

Bug Fixes

• perf(ci): install hyperfine prebuilt instead of compiling from source (#138)

v5.0.3

[5.0.3] - 2026-06-13

Bug Fixes

• fix(action): pass untrusted inputs via env to prevent shell template injection (#135)

v5.0.2

[5.0.2] - 2026-05-22

Bug Fixes

• fix(run): base64-encode tool_configs values so multi-line content survives read (#125)

v5.0.1

[5.0.1] - 2026-05-19

Bug Fixes

• fix(run): strip binary before measuring size (#122)

v5.0.0

[5.0.0] - 2026-05-19

Breaking Changes

• feat!: ship v4 — install_sizes field, standard-version + commit-and-tag-version, drop footer

Bug Fixes

• fix(release): switch to PR mode so branch-protected main accepts auto-releases (#120)

v4.0.0

First major bump since v3 (April 2026). Rolls up two changes since v3.1.2 that consumers need to handle:

Breaking

• latest.json gains an install_sizes field (#117) keyed by tool with {npm?, binary?} shape. Consumers that parse the JSON structure may need to handle the new key gracefully.
• tools.json extended from 3 to 5 competitor tools (#115) — emitted benchmark keys now include standard-version-* and commit-and-tag-version-* rows.
• format-release.sh no longer emits the trailing *Binary size: X MB — ferrflow Y* footer (#117). The line was double-prefixed ("ferrflow ferrflow Y") and the version was always stale because the bench artifact is captured before the release commit bumps it. The Install footprint section added in #117 is the canonical place for size info now.

What it unblocks downstream

• ferrflow.com/performance gains the Install footprint section the moment the next sync runs (the conditional in FerrFlow-Cloud/performance.astro renders only when install_sizes is present).
• The perf table picks up standard-version and commit-and-tag-version columns alongside the existing 3 (changesets, semantic-release, ferrflow).

Consumers

FerrLabs/FerrFlow ci.yml needs its pin bumped from @v3 to @v4. Follow-up PR incoming.