Consider tagging module "tsne"?

[Rick-xuy]

I found that package github.com/danaugrs/go-tsne/tsne is placed in module github.com/danaugrs/go-tsne/tsne.

However, it seems that module github.com/danaugrs/go-tsne/tsne 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/danaugrs/go-tsne/tsne, downstream would depends on pseudo-version of module github.com/danaugrs/go-tsne/tsne.

github.com/danaugrs/go-tsne/tsne v0.0.0-20220306153449-0ee45704632c

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 module tsne properly. For example, tsne/v0.0.1, tsne/v1.0.0etc, so that other project can use tag to import this module in go.mod.

[JuanVargas]

You submitted the issue on Feb 17, 2023. There is no evidence that your issue received a response since then. Is this code dead?