tree 92f6494f3409578dfca1a473bc96152b6e19d15f
parent 3da734a83f7d6126b377fbe9e8855474c10377b6
author Jonathan Amsterdam <jba@google.com> 1630070941 -0400
committer Jonathan Amsterdam <jba@google.com> 1630517578 +0000

internal/postgres: keep only one module major version in search grouping

When grouping search results by module, keep only the highest-scoring
package from the highest tagged major version.

Previously, we kept all major versions, and only ranked the higher one
first, so as not to lose information (like import counts) for
higher-scoring packages in a lower major version. But the results are
unexpected.

Fixes golang/go#47839

Change-Id: I66dedec470dd1588f02dcfed5604a6e63f020d62
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/345611
Trust: Jonathan Amsterdam <jba@google.com>
Run-TryBot: Jonathan Amsterdam <jba@google.com>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Julie Qiu <julie@golang.org>