go.dev: allow force-refresh of package just like on godoc.org

[JAicewizard]

What is the URL of the page with the issue?

https://pkg.go.dev/mod/github.com/jaicewizard/tt

What is your user agent?

Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0

Screenshot

N/A

What did you do?

I wanted to force refresh pkg.go.dev to show the latest version of my package

What did you expect to see?

a button to refresh just like on godoc.org

What did you see instead?

No button

[julieqiu]

Closing as a duplicate of #37106.

[aaronsky]

what issue was this originally supposed to be a duplicate of? The link to #37106 no longer works

[julieqiu]

It looks like that issue was deleted, so I'll reopen this one.

@aaronsky - would you mind elaborating your use case for a refresh button on pkg.go.dev?

[aaronsky]

Thanks! I recently released v0.1.0 of my brand new package asc-go. I currently have a cached version of HEAD as the only sole version on pkg.go.dev. GoDoc has already updated to reflect the new documentation, but I have been struggling to get pkg.go.dev to update. Based on my searches this seems like a fairly common issue with pkg.go.dev. If a refresh button is out of the question due to technical concerns, more guidance on how often the package index is updated and how to affect that index as a package author would be helpful.

[aaronsky]

Ah, I see it just refreshed. Can you say what triggered that reindexing?

[julieqiu]

Can you say what triggered that reindexing?

My guess is that someone made a request to proxy.golang.org/github.com/aaronsky/asc-go/@latest, either by visiting the URL directly or by using the Go command. proxy.golang.org and https://golang.org/cmd/go/#hdr-Module_downloading_and_verification have more information on this topic.

We monitor https://index.golang.org/index regularly for new modules to add to pkg.go.dev. See our design doc.

GoDoc has already updated to reflect the new documentation, but I have been struggling to get pkg.go.dev to update. Based on my searches this seems like a fairly common issue with pkg.go.dev.

In general, are you looking for the latest version (i.e. the version returned by https://proxy.golang.org/github.com/aaronsky/asc-go/@latest), or the master version (i.e. https://proxy.golang.org/github.com/aaronsky/asc-go/@v/master.info)?

Pkg.go.dev supports both (see #36811 and #37002 for details). When you make a request to https://pkg.go.dev/github.com/aaronsky/asc-go@master, we will automatically refetch and refresh the master version, when that request is made.

If a refresh button is out of the question due to technical concerns, more guidance on how often the package index is updated and how to affect that index as a package author would be helpful.

If the above doesn't answer your question, or you have suggestions for better documentation or addressing a specific use case, let me know.

[aaronsky]

Interesting. I was requesting https://proxy.golang.org/github.com/aaronsky/asc-go/@v0.1.0 and that wasn't working. I'll make a personal note to try latest from now on, since that's usually what I expect when refreshing my package page. Thank you!

[julieqiu]

Happy to help!

I was requesting https://proxy.golang.org/github.com/aaronsky/asc-go/@v0.1.0 and that wasn't working.

The syntax is https://proxy.golang.org/github.com/aaronsky/asc-go/@v/v0.1.0.info (see https://golang.org/cmd/go/#hdr-Module_proxy_protocol). You can also visit https://pkg.go.dev/github.com/aaronsky/[email protected], now that #36811 is live, and click the Request <your-package> button.

Closing this issue - feel free to open a new one if anything comes up.