Repository navigation
feat(ci): enable competitor benchmarks (semantic-release, changesets) in release run - #451
Merged
Merged
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Benchmark
Details
| Benchmark suite | Current: 20b5e67 | Previous: 0b5fe57 | Ratio |
|---|---|---|---|
git_find_tag/100 |
1354598 ns/iter (± 8805) |
||
git_find_tag/1000 |
13630722 ns/iter (± 67735) |
This comment was automatically generated by workflow using github-action-benchmark.
This was referenced May 19, 2026
BryanFRD
added a commit
that referenced
this pull request
May 19, 2026
Wires up runtime benchmarks for changesets, semantic-release, standard-version and commit-and-tag-version. Without these configs the runner's pre-flight validation step silently skipped every non-ferrflow tool, so the perf page only ever showed ferrflow rows even after #451 flipped skip-competitors off. Closes #452
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The full benchmark job (
FerrLabs/Benchmarks@v3withtype: full) runs on everymainpush and produces a hyperfine timing table per fixture × per tool, plus binary/install size. The infrastructure has supported comparison against semantic-release / changesets / release-please for a long time, but the FerrFlow CI invoked it withskip-competitors: true— so every release shipped with a comparison table that only had one row (FerrFlow itself).Flipping the flag enables the actual comparison so next release notes include side-by-side timings.
Cost
The benchmark job is gated by
if: github.event_name == 'push' && github.ref == 'refs/heads/main'— it never runs on PRs. So enabling competitors adds time to release runs only, not to PR latency.Approximate added time per release: 5-10 minutes (npm install for each competitor + hyperfine across 4 fixtures × 2 npm-installed competitors). Acceptable given how rarely it triggers.
Output
Each
mainpush (= each release) will now produce:benchmark-release-summaryartifact)hyperfine-baselineartifact (90-day retention, fetchable viaghAPI for any future public-facing page)Follow-up
Once a couple of releases produce real data, open a follow-up to surface the comparison publicly (e.g.
/comparepage on ferrflow.com pulling the artifact at build time).