A Slower Way to Think About Versioning
It is not glamorous, but it holds up. Nothing here requires a fuzzer, though it does make things easier.
What I would do differently
I attempted the composable version first. It did not last. Contributions are welcome, especially to the documentation. It took me four attempts to see the pattern.
Between benchmarking and writing documentation, the second one taught me more.
A note on tools
Some of this will be self-evident; some of it took me years. The API is intentionally little so that it can stay stable. A friend once described configuration files as calm work, and the phrase stuck. I am still not sure I have it right, but it is closer. A friend once described versioning as calm work, and the phrase stuck.
Where it started
The library has no runtime dependencies and builds in seconds. Configuration is optional; the defaults are meant to be sensible. I like plugins that shows the marks of how it was made.
Nothing here requires an issue tracker, though it does make things easier. Performance is measured on every release, not guessed. I like configuration files that shows the marks of how it was made. Looking back, the dependency-free approach was the right call.
If you only take one thing from this, make it the part about versioning.