Merge pull request #1195 from DavidT3/bug/PyPIActionsNotWorking

Updating some action versions in the publishing actions, as well as t…

.github/workflows/publish_to_pypi.yml

@@ -18,20 +18,20 @@ jobs:
   # The only job in this action, building and publishing the XGA Python module
   build-n-publish:
     name: Build and publish XGA
-    # The build/publishing process runs on Ubuntu 20.04 - not super important what this is for this use case, so long as its not Windows
-    runs-on: ubuntu-20.04
+    # The build/publishing process runs on the latest Ubuntu - not super important what this is for this use case, so long as its not Windows
+    runs-on: ubuntu-latest
 
     # This job has several steps
     steps:
       # Checks out the master branch (what we want to build and publish - hopefully with the VCS info that versioneer needs), then 
       #  activates a relatively recent version of Python
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v4
       with:
         fetch-depth: 0
     - name: Setup the Python install
-      uses: actions/setup-python@v1
+      uses: actions/setup-python@v4
       with:
-        python-version: 3.7
+        python-version: 3.12
 
     # The next two chunks set up PIP properly and build the module
     - name: Install pypa/build

.github/workflows/publish_to_test_pypi.yml

@@ -23,20 +23,20 @@ jobs:
     name: Build and publish XGA
     # I actually only want to run this one if the pushed commit has a tag - I will only do this for new versions of the module
     if: startsWith(github.ref, 'refs/tags')
-    # The build/publishing process runs on Ubuntu 20.04 - not super important what this is for this use case, so long as its not Windows
-    runs-on: ubuntu-20.04
+    # The build/publishing process runs on the latest version of Ubuntu - not super important what this is for this use case, so long as its not Windows
+    runs-on: ubuntu-latest
 
     # This job has several steps
     steps:
       # Checks out the master branch (what we want to build and publish - hopefully with the VCS info that versioneer needs), then 
       #  activates a relatively recent version of Python
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v4
       with:
         fetch-depth: 0
     - name: Setup the Python install
-      uses: actions/setup-python@v1
+      uses: actions/setup-python@v4
       with:
-        python-version: 3.7
+        python-version: 3.12
 
     # The next two chunks set up PIP properly and build the module
     - name: Install pypa/build