/cc @julieqiu @jba @jamalc

See the instructions under "Adding a package" on https://go.dev/about. Basically, someone has to go get a version through the proxy for us to eventually see it. We haven't seen 09b... yet.

Thanks and I did get this to work by visiting https://proxy.golang.org/github.com/gotailwindcss/tailwind/@latest and then https://proxy.golang.org/github.com/gotailwindcss/tailwind/@v/18fbd6a.info and then waiting for a bit.

Can I suggest something like the following to make this process more obvious:

• A link on the Overview page for the package, perhaps called something like "Update this Package".
• That link should give a simple URL at proxy.golang.org to cause such an update to occur, rather than requiring the maintainer to construct it.
• It should cover how repos that do not yet have explicit version numbers work (common for new projects just being created before they have a roadmap). E.g. I'm still not clear on which of the above URLs caused the update, because of the caching. I'm sure I could carefully read through the documentation on proxy.golang.org to figure out exactly what happened, but...
• I also hazard that it should not require me to have to understand how proxy.golang.org works in order to use it.
• It should set the expectation that there is a cache timeout for the new update to appear.

My rationale on this is that as a maintainer, the most common thing I would want to do with pkg.go.dev is "update this to the latest", and while now I understand more about the process, it has not been particularly obvious how all this is supposed to work, and specifically what I need to do as a maintainer to get my stuff to show up as quickly as possible.

If you visit the URL path YOUR_MODULE@master, it will 404 with a button to load the latest version.

We can consider putting that button on the overview page.

Closing this issue, since https://pkg.go.dev/github.com/gotailwindcss/tailwind has been updated. I'll open a separate issue for the suggestions in #41055 (comment).