chore: release v3.1.0

The manifest has been at 3.x since the two feat! commits (#1, #2), but
releases kept being cut as v1.0.x. Since the workflow publishes the
manifest version rather than the tag, the release labelled v1.0.5 in fact
published 3.0.0 to PyPI, and the next v1.0.x release then failed.

Bump to 3.1.0 for the additive changes since 3.0.0 (#3, #4, #5) and fail
the publish job up front when the release tag, pyproject.toml version and
__version__ disagree.

Author: preaverage

.github/workflows/publish.yml

@@ -29,6 +29,16 @@ jobs:
       - uses: actions/setup-python@v5
         with:
           python-version: "3.12"
+      - name: Verify release tag matches pyproject.toml version
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          proj="$(python -c "import tomllib;print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")"
+          dunder="$(grep -oP '(?<=^__version__ = ")[^"]+' src/pkmnprices/__init__.py)"
+          if [ "$tag" != "$proj" ] || [ "$proj" != "$dunder" ]; then
+            echo "::error::Version mismatch — tag $GITHUB_REF_NAME, pyproject.toml $proj, __version__ $dunder."
+            echo "PyPI publishes the manifest version, not the tag. Bump pyproject.toml or retag as v$proj."
+            exit 1
+          fi
       - run: pip install build
       - run: python -m build
       - uses: pypa/gh-action-pypi-publish@release/v1

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pkmnprices"
-version = "3.0.0"
+version = "3.1.0"
 description = "Python client for the Pkmn Prices API"
 readme = "README.md"
 license = "MIT"

src/pkmnprices/__init__.py

@@ -31,7 +31,7 @@
     TcgplayerListing,
 )
 
-__version__ = "3.0.0"
+__version__ = "3.1.0"
 
 __all__ = [
     "PkmnPrices",