RepoJournal
Go

@golang

Go and the standard library — backend infrastructure at scale

Pick a date

  1. Fri 1 may
  2. Sat 2 may
  3. Sun 3 may
  4. Tue 5 may
  5. Wed 6 may
  6. Thu 7 may
  7. Fri 8 may
  8. Sat 9 may
  9. Sun 10 may
  10. Mon 11 may
  11. Tue 12 may
  12. Wed 13 may
  13. Thu 14 may
  14. Fri 15 may
  15. Sat 16 may
  16. Sun 17 may
  17. Mon 18 may
  18. Tue 19 may
  19. Wed 20 may
  20. Thu 21 may
  21. Sat 23 may
  22. Tue 26 may
  23. Wed 27 may
  24. Thu 28 may
  25. Fri 29 may
  26. Sat 30 may
  27. Sun 31 may
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

PKGSITE LIFTS QUERY LIMITS, EXPOSES MODULE TIMESTAMPS

By RepoJournal · Filed · About Go

Go's package discovery API just got faster and more informative—hardcoded constraints are gone, and clients can now read version timestamps directly from module metadata.

The biggest change lands in the internal/api layer where a hardcoded limit on GetImportedBy queries is being removed [1], letting you actually fetch the full dependency graph without pagination walls. In the same pass, the /module/{path} endpoint now exposes commitTime in the v1beta spec [2], meaning you no longer need a separate call to the /versions endpoint to find when a module version was published—the timestamp comes straight from the module proxy. Search pagination tightened up too: the default limit dropped to 25 results [3] to align with frontend expectations and shave milliseconds off first-page load. The CLI tooling got its own fixes [4], ensuring the packages command actually prints results, and the codebase ran through go fix [5] to catch any lurking issues.

Action items

References

  1. [1] internal/api: remove limit on GetImportedBy ServePackageImportedBy golang/pkgsite
  2. [2] internal/api: expose commitTime in module metadata golang/pkgsite
  3. [3] internal/api: set default search pagination limit to 25 golang/pkgsite
  4. [4] cmd/internal/pkgsite-cli/client: fix packages command golang/pkgsite
  5. [5] all: run go fix ./... golang/pkgsite

FAQ

What changed in Go on May 10, 2026?
Go's package discovery API just got faster and more informative—hardcoded constraints are gone, and clients can now read version timestamps directly from module metadata.
What should Go teams do about it?
Check if you're hitting imported-by limits in production queries—you may now be able to remove workarounds • Update client code consuming the /module endpoint to take advantage of commitTime field
Which Go repositories shipped on May 10, 2026?
golang/pkgsite

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.