x/pkgsite: package removal request for github.com/DataDog/datadog-agent

[djmitche]

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

github.com/DataDog/datadog-agent (but not sub-packages such as github.com/DataDog/datadog-agent/pkg/util/log)

Are you the owner of this package?

Yes, I am on the agent-core team at DataDog, as the GitHub team membership confirms.

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

We are seeing an old tag at https://pkg.go.dev/github.com/DataDog/datadog-agent, but would like to see the latest and greatest in that package.

The package is public, but not intended for linkage by other go projects: we don't guarantee any sort of API compatibility. So, we would prefer to have it appear un-versioned, with just the latest commit to main appearing. My understanding is that the only way to retract a version is to publish a new version.

[seankhliao]

You can publish a higher version and retract it at the same time, eg v0.8.1 which retracts both v0.8.0 and v0.8.1

[jamalc]

Package removal can only be applied to all versions (tagged and untagged) of the package and includes sub-packages. To have it appear un-versioned follow @seankhliao's suggestion.

[djmitche]

As a followup for the next person to see this -- note that while the above works for go list and other commands, it does not cause the pkg.go.dev site to begin showing the latest version on the main branch. Instead, it shows the latest (retracted) version with a "RETRACTED" banner, and clicking "latest" brings you to a list of published versions. So basically, once you tag a Git repo, there's no going back to un-tagged docs.

[djmitche]

It appears that there was some daily (or weekly?) job that ran that fixed things, as https://pkg.go.dev/github.com/djmitche/proj is again showing the latest from the default branch.