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
No "latest version" warning (as of writing v0.11.1 is the latest version).
What did you see instead?
Red "latest version" button linking to a very outdated version.
Cause?
While trying to figure out the best way to publish a package in a subdirectory, I tried a bunch of configurations of "root go.mod module in a subdirectory", "go.mod in root and child directory", etc.
Eventually I settled on a single go.mod in the parent directory.
pkg.go.dev remembers one of these old attempts as the newest version for this subdirectory package which is confusing to users and means I can't link to it to point to the latest version (currently the latest version is here).
I tried to retract the old version but it's a git hash pseudoversion and I wasn't able to get it to 'forget' the old package.
Is there any way to get the site to prefer my newer parent package instead?
The text was updated successfully, but these errors were encountered:
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
What is the URL of the page with the issue?
https://pkg.go.dev/github.com/trealla-prolog/go@v0.11.1/trealla
What is your user agent?
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36
Screenshot
What did you do?
Accessed the "trealla" subpackage from this URL: https://pkg.go.dev/github.com/trealla-prolog/go#section-directories
What did you expect to see?
No "latest version" warning (as of writing v0.11.1 is the latest version).
What did you see instead?
Red "latest version" button linking to a very outdated version.
Cause?
While trying to figure out the best way to publish a package in a subdirectory, I tried a bunch of configurations of "root go.mod module in a subdirectory", "go.mod in root and child directory", etc.
Eventually I settled on a single go.mod in the parent directory.
pkg.go.dev remembers one of these old attempts as the newest version for this subdirectory package which is confusing to users and means I can't link to it to point to the latest version (currently the latest version is here).
I tried to retract the old version but it's a git hash pseudoversion and I wasn't able to get it to 'forget' the old package.
Is there any way to get the site to prefer my newer parent package instead?
The text was updated successfully, but these errors were encountered: