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.

Sign up for GitHub

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

Jump to bottom

x/pkgsite: package removal request for github.com/NeuraLegion/sectester-go@v1.0.0 #58852

Closed
derevnjuk opened this issue Mar 3, 2023 · 5 comments
Closed

x/pkgsite: package removal request for github.com/NeuraLegion/sectester-go@v1.0.0 #58852

derevnjuk opened this issue Mar 3, 2023 · 5 comments
Labels
FrozenDueToAge pkgsite
Milestone
Unreleased

Comments

@derevnjuk
Copy link

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

The package version is v1.0.0 under the following module path: github.com/NeuraLegion/sectester-go

Are you the owner of this package?

Author, Owner, and actual Publisher

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

Due to the workflow misconfiguration, the initial development release has been tagged by v1.0.0 instead of the expected v0.1.0. We would like to remove this package version from the pkg.go.dev website, to avoid any confusion. Retracting the particular stable version, we will have to bump it up to v2.x.x. later on.
@gopherbot gopherbot added this to the Unreleased milestone Mar 3, 2023
@seankhliao
Copy link
Member

we can't remove singular versions for you.
you can publish v1.0.1 and retract both v1.0.0 and v1.0.1 at the same time

@seankhliao seankhliao closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2023
@derevnjuk
Copy link
Author

@seankhliao, I am unable to release any version of the package without the reason, as the version number is automatically determined based on the changes made, following the semantic versioning (semver) guidelines. Is it possible to remove the whole package then?

@derevnjuk
Copy link
Author

Should I open a new issue then?

@seankhliao
Copy link
Member

the repo still exists, please use retract

@derevnjuk
Copy link
Author

@seankhliao The package was published for the first time yesterday and is currently in the early stages of development. As such, the initial version should be labeled as v0.0.1 instead of v1.0.0. Since the package has yet to be utilized and is not expected to be used for the next few months, there doesn't seem to be any compelling reason why you couldn't remove the specific version or even the entire package from the registry.

derevnjuk added a commit to NeuraLegion/sectester-go that referenced this issue Mar 5, 2023
@derevnjuk
build: retract v1.0.0 version
dd1fc1b 
Due to the misconfiguration, the initial development release has been tagged by v1.0.0 instead of the expected v0.1.0.

For details please refer to the GitHub issue at golang/go#58852
@derevnjuk derevnjuk mentioned this issue Mar 5, 2023
Merged
derevnjuk added a commit to NeuraLegion/sectester-go that referenced this issue Mar 5, 2023
@derevnjuk
build: retract v1.0.0 version (#12)
a52a9c1 
Due to the misconfiguration, the initial development release has been
tagged by v1.0.0 instead of the expected v0.1.0.

For details please refer to the GitHub issue at golang/go#58852
@golang golang locked and limited conversation to collaborators Mar 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge pkgsite
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@gopherbot @seankhliao @derevnjuk