Skip to content

Version number mismatch #7748

@maresb

Description

@maresb

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:

Image

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.

  1. Yank the release on PyPI
  2. Delete the v5.21.2 and v5.22.0 GitHub tags
  3. Delete and recreate the v5.22.0 GitHub release

Keep the PyPI release

  1. Delete the v5.21.2 GitHub tag
  2. 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.
  3. Delete the v5.22.0 GitHub tag
  4. Delete and recreate the v5.22.0 GitHub release

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions