I suggest to make the tagging not a manual git tag process, but something driven my the source version, similar how we do it in UHDM and Surelog, in which the version number is mentioned in the CMakeLists.txt and the tag is then auto-generated in the CI if it changed.
In our case, this would be a variable in the toplevel Makefile which then is compiled into #define into every module, so that it is is possible to ask the module about their version.
Then, the tagging itself will be automatic, e.g. similar how we do it in UHDM
For people packaging, it is useful to refer to a tag or release, as referring to a commit makes it harder to see the rough relative release date.
Currently, the last tag is from almost 3 years ago: https://github.com/chipsalliance/yosys-f4pga-plugins/tags
I suggest to make the tagging not a manual git tag process, but something driven my the source version, similar how we do it in UHDM and Surelog, in which the version number is mentioned in the CMakeLists.txt and the tag is then auto-generated in the CI if it changed.
In our case, this would be a variable in the toplevel Makefile which then is compiled into
#define
into every module, so that it is is possible to ask the module about their version.Then, the tagging itself will be automatic, e.g. similar how we do it in UHDM