-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Description
Description
@ricardoV94, I was wondering why the conda-forge autotick bot didn't trigger for the latest release and I noticed a peculiarity. I don't think this is particularly urgent, but we should figure out a strategy here.
There are two Git tags corresponding to the same commit of the latest release:
As a result, while the GitHub release corresponds to PyMC v5.22.0, the corresponding PyPI package is v5.21.2.
I think there are two straightforward ways to resolve this:
Yank the PyPI release
I'd personally prefer the other method since yanking is fairly disruptive, and the violation of our versioning convention is fairly minor.
- Yank the release on PyPI
- Delete the v5.21.2 and v5.22.0 GitHub tags
- Delete and recreate the v5.22.0 GitHub release
Keep the PyPI release
- Delete the v5.21.2 GitHub tag
- Cut a new GH release for v5.21.2 unchecking "Set as the latest release", and adding the following in the release notes, incl.
>characters:> [!IMPORTANT] > This was an erroneous duplicate release of v5.22.0.
- Delete the v5.22.0 GitHub tag
- Delete and recreate the v5.22.0 GitHub release
Metadata
Metadata
Assignees
Labels
No labels
