Fix Github "released version" mismatch with actual release version

[bunny-therapist]

Every time there is a new release of arcade, I see something like this:

and then I go to install that new version of arcade, and it does not work. Then I remember that I always have to subtract one from the version. If it says that 3.0.0.dev42 is released, it means that 3.0.0.dev41 is released.

The same mismatch is also visible on the main repo page (bottom right):

This ticket is a request to make it so that the version that is announced and listed on Github matches the version that is actually available on PyPI.

Other python projects do not have this problem. For example, see

• pytest: https://pypi.org/project/pytest/#history latest version matches https://github.com/pytest-dev/pytest/releases/tag/8.3.4
• flake8: https://pypi.org/project/flake8/#history matches https://github.com/PyCQA/flake8/tags
• pyglet: https://pypi.org/project/pyglet/#history matches https://github.com/pyglet/pyglet/releases/tag/v2.1.0

[bunny-therapist]

I included the examples because I have raised this issue before on discord but I got the impression that this mismatch was seen as something normal and then it was never addressed. They may also give some inspiration for how to solve it.

[einarf]

We should fix this. It's confusing. It's ok to bump version in the toml but a tag should not be created until the that version is released because the tag is something you should be able to check out to obtain that version.

It's an automation bug. Scripts needs tweaking.