I found that package github.com/efficientgo/tools/extkingpin is placed in submodule github.com/efficientgo/tools/extkingpin.
However, it seems that module github.com/efficientgo/tools/extkingpin is not tagged. According to Go Modules wiki, submodule should be tagged like relative-path-to-root/vX.X.X.
At now, when trying to import package github.com/efficientgo/tools/extkingpin, downstream would depends on pseudo-version of module github.com/efficientgo/tools/extkingpin.
github.com/efficientgo/tools/extkingpin v0.0.0-20221005154214-b82254effbb1
I think it is not very readable and difficult to upgrade. This is not conductive to version control either.
So, I propose whether it is possible to tag the module github.com/efficientgo/tools/extkingpin. For example, extkingpin/v0.0.1, extkingpin/v1.0.0etc, so that other project can use tag to import this module in go.mod.
I found that package
github.com/efficientgo/tools/extkingpinis placed in submodulegithub.com/efficientgo/tools/extkingpin.However, it seems that module
github.com/efficientgo/tools/extkingpinis not tagged. According to Go Modules wiki, submodule should be tagged likerelative-path-to-root/vX.X.X.At now, when trying to import package
github.com/efficientgo/tools/extkingpin, downstream would depends on pseudo-version of modulegithub.com/efficientgo/tools/extkingpin.I think it is not very readable and difficult to upgrade. This is not conductive to version control either.
So, I propose whether it is possible to tag the module
github.com/efficientgo/tools/extkingpin. For example,extkingpin/v0.0.1,extkingpin/v1.0.0etc, so that other project can use tag to import this module in go.mod.