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

There is a tag v2.52.1 with no release or Docker images #14291

Closed
remram44 opened this issue Jun 12, 2024 · 7 comments
Closed

There is a tag v2.52.1 with no release or Docker images #14291

remram44 opened this issue Jun 12, 2024 · 7 comments

Comments

@remram44
Copy link

What did you do?

Noticed tag 2.52.1, tried to install it

What did you expect to see?

Prometheus running

What did you see instead? Under which circumstances?

ImagePullBackOff

System information

No response

Prometheus version

No response

Prometheus configuration file

No response

Alertmanager version

No response

Alertmanager configuration file

No response

Logs

No response

@beorn7
Copy link
Member

beorn7 commented Jun 12, 2024

This was tagged for a planned release, but then we never cut a release. Mostly because 2.53 is already underway.

@ArthurSens maybe you want to delete the tag, as we probably will never cut that release?

@ArthurSens
Copy link
Member

ArthurSens commented Jun 12, 2024

Can this be done safely though? Should I add a retract directive to go mod before that?

For extra context, there's an extensive slack thread with all the problems we faced in that release 😕

@beorn7
Copy link
Member

beorn7 commented Jun 12, 2024

I think you can safely delete the 2.52.1 tag because Go will only see the 0.52.1 tag, which you could leave in place.

@ArthurSens
Copy link
Member

Yeah ok, I was trying to add the retract directive to v2.52.1 and the compiler was complaining about that... I'll just remove the tag then :)

@ArthurSens
Copy link
Member

Done, sorry for the inconvenience @remram44!

rxrbln pushed a commit to rxrbln/t2sde that referenced this issue Jun 16, 2024
@oseiberts11
Copy link

For extra context, there's an extensive slack thread with all the problems we faced in that release 😕

Referring to a place where you need to login to read anything isn't very helpful, I'm afraid. Apart from the fact that a chat system simply isn't documentation.

@beorn7
Copy link
Member

beorn7 commented Jun 18, 2024

To clarify in case others feel like missing out: What @ArthurSens linked to, isn't documentation. Just informational context and (literally) chat.

Having said that, I agree that even for "mere" chat, Slack is really a bad fit for an open source project. But everyone knows that already. It's a problem we cannot solve in the scope of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants