You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: