Automating Release Flow

[timonrieger]

Hey there!

I just saw #139, took a look at the codebase and wondered whether there is a reason, for not automating the release process?

I see you use the main branch more like a "WIP" until the maintainers decide to release a new version. Just curious what the intention behind it is.

I have experience integrating automated release flows for python packages and can recommend it as it makes the release process deterministic and new features/patches become available earlier 😄

[timonrieger]

Following up on this: one option that could work well here is using automated releases driven by PR titles. The flow would be:

• Use squash-and-merge.
• Maintain or adjust the PR title to follow Conventional Commits (fix:, feat:, etc.).
• Let a tool like Python Semantic Release determine the version bump and publish automatically whenever something lands on main.

Contributors don’t need to format every commit, and maintainers keep full control by simply editing the final squash message. This keeps friction low while making releases deterministic and frequent.

If that sounds useful, I’m happy to help set up the configuration!