search

openshift / api

Canonical location of the OpenShift API definition.
http://www.openshift.org
Apache License 2.0
94 stars 516 forks source link

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

Closed mx-psi closed 6 months ago

mx-psi commented 1 year ago

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:

Some related issues for this specific version:

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 commented 12 months ago

It was retracted

https://github.com/openshift/api/commit/abb98ff04d03d5d3444b6e49f26c36c0b37e0e03

mx-psi commented 12 months ago

@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 commented 9 months ago

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 commented 8 months ago

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 commented 7 months ago

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 commented 6 months ago

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[bot] commented 6 months ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/api/issues/1661#issuecomment-2084649716): >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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.