I found that module github.com/skydive-project/skydive/graffiti is a submodule of skydive.
However, it seems that submodule github.com/skydive-project/skydive/graffiti is not tagged. According to Go Modules standard , submodule should be tagged like relative-path-to-root/vX.X.X.
At present, when trying to import the package, downstream project would have to depend on pseudo-version of it and cannot get a valid tag version.
Would you consider tagging the submodule according to Go standard, for example, releasing a tag `graffiti/v0.28.0``, so that we can use tag version to import this module in go.mod?
I found that module
github.com/skydive-project/skydive/graffiti
is a submodule ofskydive
.However, it seems that submodule
github.com/skydive-project/skydive/graffiti
is not tagged. According to Go Modules standard , submodule should be tagged like relative-path-to-root/vX.X.X. At present, when trying to import the package, downstream project would have to depend on pseudo-version of it and cannot get a valid tag version.Would you consider tagging the submodule according to Go standard, for example, releasing a tag `graffiti/v0.28.0``, so that we can use tag version to import this module in go.mod?