update test matrix to include python 3.13

.github/workflows/test.yml

@@ -1,5 +1,7 @@
 name: Test
 
+# note: when updating the matrix, make sure the `workflow_dispatch` and `generate-matrix` entries match
+
 on:
   workflow_dispatch:
     inputs:
@@ -15,13 +17,12 @@ on:
       python_version:
         type: choice
         description: Python version to test with
-        default: '3.12'
+        default: '3.13'
         options:
         - 'all'
         - '3.9'
-        - '3.10'
-        - '3.11'
-        - '3.12'
+        - '3.13'
+        - '3.13t'
         - 'pypy3.9'
         - 'pypy3.10'
       test_specification:
@@ -57,9 +58,8 @@ jobs:
         - windows-latest
       PYTHON_VERSION: |
         - '3.9'
-        - '3.10'
-        - '3.11'
-        - '3.12'
+        - '3.13'
+        - '3.13t'
         - 'pypy3.9'
         - 'pypy3.10'
     steps:
@@ -153,7 +153,8 @@ jobs:
       - uses: actions/checkout@v4
         with:
           submodules: recursive
-      - uses: actions/setup-python@v5
+      #- uses: actions/setup-python@v5  # does not currently support 3.13t https://github.com/actions/setup-python/issues/771
+      - uses: Quansight-Labs/setup-python@v5
         with:
           python-version: ${{ matrix.platform.python-version }}
           cache: "pip"

Contributing.md

@@ -50,5 +50,5 @@ a PR, but generally stick to conforming to the suggested linter rules.
 2. Update `Changelog.md` to reflect the new changes.
 3. Check out the commit you want to make a release from.
 4. Run `git tag <version>` e.g. `git tag v0.1.0`.
-5. Run `git push origin <version>` e.g. `git tag v0.1.0`.
+5. Run `git push origin <version>` e.g. `git push origin v0.1.0`.
     - This will trigger the 'release' github action which will upload to PyPi.