Comparison
Why FerrFlow?
A single native binary, language-agnostic across 14+ manifest formats, driven purely by conventional commits. Here is how it lines up against the JavaScript-ecosystem release tools, feature by feature.
| FerrFlow | semantic-release | release-please | Changesets | |
|---|---|---|---|---|
| Commits & versioning | ||||
| Conventional-commits driven | ✓ | ✓ | ✓ | — |
| SemVer bump from history | ✓ | ✓ | ✓ | ~ |
| No changeset files to author | ✓ | ✓ | ✓ | — |
| Language coverage | ||||
| 14+ manifest formats Cargo, npm, pyproject, Chart.yaml, mix, gemspec, pubspec… | ✓ | ~ | ✓ | — |
| Monorepo, multi-package | ✓ | ~ | ✓ | ✓ |
| Output | ||||
| Changelog generation | ✓ | ✓ | ✓ | ✓ |
| Git tag + GitHub Release | ✓ | ✓ | ✓ | ✓ |
| Release-PR workflow | ~ | — | ✓ | ✓ |
| Runtime & DX | ||||
| Single static binary, no Node runtime | ✓ | — | — | — |
| Native performance, no Node cold start | ✓ | — | — | — |
| Ships as a GitHub Action | ✓ | ✓ | ✓ | ✓ |
| Free / open source | ✓ | ✓ | ✓ | ✓ |