Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
x/pkgsite: don't imply that vN.x.y is the latest version when vN+1 exists #37765
What is the URL of the page with the issue?
For example: https://pkg.go.dev/github.com/cespare/xxhash?tab=doc
What is your user agent?
What did you do?
Viewed the v1 documentation for a module that also has a v2.
What did you expect to see?
No v1 version of my module should be marked as "Latest" since v2 exists.
What did you see instead?
v1.1.0 was marked as "Latest".
I understand that v1 and v2 are essentially two different modules, and that the discovery site is showing that v1.1.0 is the latest version of the v1 module. However, this may mislead users into thinking that v1.1.0 is somehow up-to-date. I do not want new users of my module to use v1.1.0; I want them to use the real latest version of the module which is v2.1.1 at the moment.
Ideally, when viewing v1.1.0, the users would see on the page that v2 exists and is the latest major module version. There ought to be a link to quickly go to the latest version, just as there is a red "Go to latest" link when viewing the not-latest-minor-version page (example):
This is related to #36969, where the search ranking also pushes users toward using the old major version of my module.
Right now it seems that the discovery site has very little notion of the relationship between different major versions of the same module. Please consider how to make this site more friendly for maintainers of v2+ modules.
I think there are two different notions of “latest” at play here.
One is “what is the latest implementation of this API?”, and for that notion,
The other is “what is the latest variant of this API that addresses the same general use-cases?”, and that notion is better answered by
It may be worthwhile to surface both of those answers in some fashion.