v3.9.0 tag is available on the official Go proxy but not on this repository

[mx-psi]

The v3.9.0 tag is available on the pkg.go.dev docs domain and the official Go proxy (download here, sumdb entry here), but it looks like the tag has been removed from this repository.

This breaks build for anyone that is not using the official Go proxy and is building a module that has v3.9.0 on their dependency tree, it breaks automatic dependency tools like Dependabot and it breaks even people pinning commits if their pseudoversion has 3.9.0 as the base version. Would it be possible for this tag to be re-added to the repository to avoid this breakage? Thanks!

Similar issues on other projects for context:

• 6.0.5851 tag is available on the official Go proxy but not on this repository ionos-cloud/sdk-go#27
• v5.0.59 tag is available on the official Go proxy but not on this repository DataDog/agent-payload#218
• v4.0.0-rc1 tag is missing go-chi/chi#713

Some related issues for this specific version:

• [Bug] Dependency github.com/openshift/api@v3.9.0+incompatible is missing grafana/grafana-operator#706
• Dependbot raised a PR to upgrade this dep to v3.9.0+incompatible but I don't see a tag with this name #1421
• Add tags for go mod compatibility #456
• go mod dependency fail when creating a new operator operator-framework/operator-sdk#2394
• build broken by openshift/api tag deletion ci-tools#414
• Cannot download go modules without go proxy devfile/devworkspace-operator#166
• [BUG] Installing kube-linter in Fedora 36 container fails stackrox/kube-linter#418

As you can see, this causes a lot of pain and has a simple solution: just add the tag back on the same commit it was before.

[OneCricketeer]

It was retracted

abb98ff

[mx-psi]

@OneCricketeer As the Go modules reference states:

Retracted versions should remain available in version control repositories and on module proxies to ensure that builds that depend on them are not broken.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[mx-psi]

This is still unsolved and still causing pain. Retracting is not enough and the Go modules reference is very clear that the current status should not happen.

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.