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
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36 Edg/80.0.361.66
Screenshot
What did you do?
Recently, I transferred ownership of a github repository from "github.com/michaelperel/docker-lock" to "github.com/safe-waters/docker-lock" and renamed all appropriate packages.
I followed the instructions on adding the package to pkg.go.dev. Specifically, I ran
GOPROXY=https://proxy.golang.org GO111MODULE=on go get github.com/safe-waters/docker-lock@v0.5.3
This command succeeds, and other projects with go modules can use this module.
However, on go.pkg.dev, I receive a strange error that github.com/safe-waters/docker-lock is not a valid go module.
What is the URL of the page with the issue?
https://pkg.go.dev/github.com/safe-waters/docker-lock
What is your user agent?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36 Edg/80.0.361.66
Screenshot
What did you do?
Recently, I transferred ownership of a github repository from "github.com/michaelperel/docker-lock" to "github.com/safe-waters/docker-lock" and renamed all appropriate packages.
I followed the instructions on adding the package to pkg.go.dev. Specifically, I ran
GOPROXY=https://proxy.golang.org GO111MODULE=on go get github.com/safe-waters/docker-lock@v0.5.3
This command succeeds, and other projects with go modules can use this module.
However, on go.pkg.dev, I receive a strange error that github.com/safe-waters/docker-lock is not a valid go module.
What did you expect to see?
Documentation for github.com/safe-waters/docker-lock identical to documentation for github.com/michaelperel/docker-lock.
What did you see instead?
go.pkg.dev displays "is not a valid package or module" error.
The text was updated successfully, but these errors were encountered: