failing to import go sdk

Help me import the Go SDK in my project.

Summary

go get github.com/microsoft/dev-tunnels/go/tunnels@latest fails with an invalid version: unknown revision 000000000000 error. This appears to be a Go modules, submodule tagging, or Go proxy resolution issue for users consuming the Go SDK from the microsoft/dev-tunnels repository.

Another Example:

go get -u github.com/microsoft/dev-tunnels/go@latest
go: github.com/microsoft/dev-tunnels/go@v0.0.0-00010101000000-000000000000: invalid version: unknown revision 000000000000

Steps to Reproduce

1. Set up a fresh Go project.
2. Run in the project directory:

   go get github.com/microsoft/dev-tunnels/go/tunnels@latest
   

   or

   go get github.com/microsoft/dev-tunnels/go@latest
   

3. Observe the error:

   go: github.com/microsoft/dev-tunnels/go@v0.0.0-00010101000000-000000000000: invalid version: unknown revision 000000000000
   

Environment

• Go version: 1.22
• Host OS: (macOS/Linux/Windows)
• Proxy: (corporate GOPROXY and/or direct)
• Behind GOPROXY

Workaround

Pin to an explicit version (e.g., v0.1.19):

go get github.com/microsoft/dev-tunnels/go/tunnels@v0.1.19

Suggestion

• Please consider always creating explicit Go module tags under the go/ subfolder and updating releases so that proxies and @latest resolutions work reliably for consumers.
• Consider documenting the required go get syntax and which versions/tags are available on pkg.go.dev.
• If use via GOPROXY is not currently supported, please clarify in the documentation and suggest workarounds or an alternate recommended installation approach.

Request

• Is it possible to ensure future releases always tag the go/ module in a way consumable via go get ...@latest and proxies?
• Can you add a troubleshooting section for Go module users in non-GitHub-mirror-only environments?

Thank you for supporting Go users!

Start by inspecting the Go module path under the go/ subfolder and the repository's release and tag configuration. Reproduce the failure with the two listed go get commands, then compare @latest resolution with the explicit v0.1.19 workaround through GOPROXY. Done means the module resolves through @latest and the supported installation and troubleshooting guidance is documented.