Technically, shipping a new version requires nothing more than merging a pull request and tagging a commit on the master branch. Versioning, packaging and everything else that is needed to build a nuget package is completely automated. And there's more than enough unit tests to guarantee the quality, so dogfooding is an exception these days. The only thing left is to create some release notes, but even that can be automated these days.
The fact of the matter is that new releases of Fluent Assertions aren't as massive as they used to be. We still get feature requests and run into occasional bug fixes obviously, but they are relatively small and have low impact. For the same reason, we're not working on the project as active as we used to be, so collecting all improvements until it's time for a major release doesn't make sense anymore.
So as of today, we'll be shipping releases of Fluent Assertions much more often, albeit with a lot less changes as prior releases. In essence, we will be practicing a form of GitHub Flow (but without the deployment part). We'll still use Semantic Versioning, so you will be able the impact of the releases from the version number.
So what do you think? Do you agree with my decision? Let me know by participating in the Disqussions below. And please follow me at @ddoomen to get regular updates on my everlasting quest for better solutions.