Hi @schmikei

Thanks again for your time.

I was wondering if it could be a better solution to do a new release each time we merge on master.

Indeed currently, it is necessary to update the contents of the file Makefile with each release and the CI does not manage very well when the release already exists and that one merges new versions of lib for example.

A simpler solution might be to take a release number prefix and add today's date to it.

So the 0.5 version prefix would produce version 0.5.230530 for May 30, 2023 and version 0.5.230601 for June 1.

This way we will never have to worry about version but we will keep the current version schema.

What do you think about it ?

What do you think about it ?

Hmm I just think that kind of goes away from the versioning principles of Golang https://go.dev/doc/modules/version-numbers

I am in favor of maybe doing a docker push for every commit to main since we are just using GHCR to host the image and tag it with the GIT SHA on merges to main.

I think dedicated releases are a good thing to follow in open source and generally have milestones that may not warrant a full on release for a feature set. But that is where my head is at/my preference :) happy to hear what your preference would be!

OK. Let's merge this for the moment.
I think it should be a good idea to use git sha to tag docker image but I don't have much time for the moment to change the Github action CI.