PyPI published version should match GitHub release

[enricogandini]

Describe the workflow you want to enable

First of all, thanks for the amazing publication and package!

I noticed there is a mismatch between the PyPI-published version (2.1.1) and the GitHub release (2.1.3).

What is the last version?

Describe your proposed solution

The versions should match, and PyPI should have the last stable version of TabPFN.

I am not sure how you publish on PyPI: do you have a GitHub Action? Do you do it manually?

Impact

As an high-quality Python package, it's nice to be able to install the last version of TabPFN via the PyPI using pip install tabpfn. Users should not need to clone the repository, checkout the tag corresponding to the last release, and install it from source.

[brendan-priorlabs]

Hi @enricogandini, thanks for the kind words. Glad you're finding TabPFN helpful! As your screenshots show, there is indeed a mismatch, but it's actually that we're ahead on PyPI (2.2.1, not 2.1.1) and behind on Github Releases. Unfortunately we haven't been consistently using that feature on Github. We have an issue in our backlog to rectify this, but for now rest assured that the code available on PyPI is the latest stable release.

[enricogandini]

Thanks for the answer, @brendan-priorlabs !

My bad, I read incorrectly the version number on PyPI. Good to know that the PyPI version is the last stable one.

[linear[bot]]

from oscar:

This is now fixed