Skip to content
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 xinhari.com/xinhari #52130

Closed
agsimfzi opened this issue Apr 3, 2022 · 3 comments
Closed

x/pkgsite: package removal request for xinhari.com/xinhari #52130

agsimfzi opened this issue Apr 3, 2022 · 3 comments

Comments

@agsimfzi
Copy link

agsimfzi commented Apr 3, 2022

What is the path of the package that you would like to have removed?

xinhari.com/xinhari

Are you the owner of this package?

Yes

What is the reason that you could not retract this package instead?

Due to lack of communication in the team we made a mistake with the first release using v1 which we ended up really regretting, so we decided again to restart the version using v0, but unfortunately when we used v0 we got v1 when running go get xinhari.com/xinhari and we also thought it would be bad for marketing because of the bad version history. So due to marketing considerations, the issue of v0 not being detected in the latest version because v1 exists and we believe no one has used our version, we sincerely request that our module be removed from pkg.go.dev instead of retracting it, so that we can start over from scratch, thanks.

@gopherbot gopherbot added this to the pkgsite/unplanned milestone Apr 3, 2022
@agsimfzi
Copy link
Author

agsimfzi commented Apr 5, 2022

Is anybody there?

@jamalc
Copy link

jamalc commented Apr 5, 2022

Removal from pkg.go.dev has no effect on the contents of the module proxy, go get xinhari.com/xinhari would still retrieve the v1 module.

Use the retract directive. This use case is outlined in the modules reference doc.

As an example, consider a case where the author of module example.com/m publishes version v1.0.0 accidentally. To prevent users from upgrading to v1.0.0, the author can add two retract directives to go.mod, then tag v1.0.1 with the retractions.

retract (
v1.0.0 // Published accidentally.
v1.0.1 // Contains retractions only.
)

@agsimfzi
Copy link
Author

agsimfzi commented Oct 11, 2022 via email

@golang golang locked and limited conversation to collaborators Oct 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants