Proposal/Question: Release frequency

First, I must say that the project is nice and quite useful and the contribution experience is smooth: Local testing is made easy, and the contributing guide is clear. So many thanks to maintainers!

Just a comment though: when a contribution is accepted, it's taken into account quickly, but release frequency is quite slow.
So, as "go-github" consumers, people have to use "snapshots" for a while if the change is needed.

What about performing a release automatically for each change made?

While performing the PR, it could be useful to identify if it's a fix, a new feature or a breaking change.
This way, while merging, it would be possible to automatically create a patch, a minor release, and a major release.

I'm motivated to contribute to this or anything else if you're interested in it!

L'issue non indica alcun file, test o punto di ingresso per le release. Inizia esaminando il processo di release corrente del repository e il modo in cui vengono pubblicate le modifiche accettate. Il lavoro sarebbe completato quando fosse disponibile un approccio concordato e implementato per classificare le modifiche e automatizzare le release corrispondenti.

Scritto dal modello di indicizzazione a partire dal testo della issue.