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

v25.0.0 release yanked #451

Closed
Antiz96 opened this issue Jan 23, 2025 · 3 comments
Closed

v25.0.0 release yanked #451

Antiz96 opened this issue Jan 23, 2025 · 3 comments

Comments

@Antiz96
Copy link

Antiz96 commented Jan 23, 2025

Hi,

I see the v25.0.0 release has been "yanked" and reported "broken" on Pypi.

We already upgraded to it at Arch Linux and some other distributions did as well, like Gentoo (cc @mgorny) and openSUSE (cc @johanneskastl) for instance.
Other distributions are also currently looking at upgrading to v25.0.0, like Alpine for instance.

Is it possible to get a bit more information about this release removal?
Is it broken enough to justify removing it from our repositories or can it wait for a new fixed release?
Is such a fixed release on its way already?

I remain available if needed.
Thanks in advance!

@ssbarnea
Copy link
Member

@Antiz96 It was yanked because it caused serious problems with molecule and we have being working since to make a new release, one that also includes fixes and preventive measures for it. Once #447 is merged, we should be able to make a new release.

I guess that you are affected because you rely on tags instead of pypi releases to retrieve the latest one. If so, we could also remove or replace the yanked tag next time this happens.

@mgorny
Copy link

mgorny commented Jan 23, 2025

To be honest, the only way to reliably notify people that they shouldn't use a release is… to make a new release instead. For Gentoo, I'm following PyPI RSS feeds for releases, and they don't report yanking at all, so I'm going to only notice another release.

gentoo-bot pushed a commit to gentoo/gentoo that referenced this issue Jan 25, 2025
Release yanked upstream due to compatibility concerns.

Bug: ansible/ansible-compat#451
Reverts: 19e09f1
Signed-off-by: Michał Górny <[email protected]>
@ssbarnea
Copy link
Member

A new release might take some time and I do not see any reasons for making another release that has the same content as the last known good, with different numbers bigger than the broken one. I am now also watching the upstream ticket.

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

No branches or pull requests

3 participants