-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/pkgsite: package removal request for github.com/kobaxidze256/go-null #58329
Comments
Hi @Kobaxidze256, I see that at pkg.go.dev the information for github.com/kobaxidze256/go-null is from 3 days ago. Is this a different module than is there now? There appear to be a couple of new tagged versions in the github repo, to get those into the module proxy (and onto pkg.go.dev) you need to make a request for the module version through the module proxy. There are a number of ways to do this and instructions on pkg.go.dev (https://pkg.go.dev/about#adding-a-package). Visiting the following should add the version to pkgsite, and you can do the same for earlier versions if you want those to appear as well: Removing this package from pkg.go.dev means that pkg.go.dev will no longer serve documentation for that package path at all, including the new module that is at that URL. I see the latest version on pkg.go.dev was 1.0.3, so if you request any of the newer versions through the proxy (as described above), the latest information for the documentation will show this newer version. |
The new package is https://pkg.go.dev/github.com/Kobaxidze256/go-null . |
Thanks for the clarification! I missed the change of case. You should be able to retract the previous versions of the module using retract as follows:
go.mod:
|
Did 1 and 2. I will do the third later. I'm expecting the old go doc page to change. |
It worked. Close the issue if you want. Thank you @suzmue! |
Thanks for following up. |
What is the path of the package that you would like to have removed?
github.com/kobaxidze256/go-null
Are you the owner of this package?
Yes.
What is the reason that you could not retract this package instead?
There's a new module where its URL points.
The text was updated successfully, but these errors were encountered: