The version number in pyproject.toml doesn't seem to be updating before a version tag is created. This means the .tar.gz archives, which are linked to those Git tags, include the wrong version number.
So the v0.1.5 tag is correct and the tags since it are one version out of date.
Looking at the commit logs, github-actions has two commits with the message "Bump version to v0.1.5" (75eba32 and 5674e67) and since then the messages have been "Bump version to v", although the commits themselves include the correct version number. However, the tag is on the commit before the bump version commit: for v0.1.10, the tag is on 643b2e9 but the version number bump is one commit later, 850fa9e. I guess this is some workflow configuration issue.
The source archive on PyPI seems to have the correct version number (I only checked v0.1.10).
The version number in pyproject.toml doesn't seem to be updating before a version tag is created. This means the .tar.gz archives, which are linked to those Git tags, include the wrong version number.
So the v0.1.5 tag is correct and the tags since it are one version out of date.
Looking at the commit logs, github-actions has two commits with the message "Bump version to v0.1.5" (75eba32 and 5674e67) and since then the messages have been "Bump version to v", although the commits themselves include the correct version number. However, the tag is on the commit before the bump version commit: for v0.1.10, the tag is on 643b2e9 but the version number bump is one commit later, 850fa9e. I guess this is some workflow configuration issue.
The source archive on PyPI seems to have the correct version number (I only checked v0.1.10).