Ci pixi lock

.github/workflows/python-publish.yml

@@ -13,9 +13,9 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@v5
     - name: Set up Python
-      uses: actions/setup-python@v4
+      uses: actions/setup-python@v6
       with:
         python-version: '3.x'
     - name: Install dependencies

.github/workflows/python-request.yml

@@ -20,9 +20,17 @@ jobs:
         shell: bash -l {0}
 
     steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@v5
     - name: Set up pixi environment
       uses: prefix-dev/setup-pixi@v0.9.1
+      with:
+        # setup-pixi runs `pixi install --locked` whenever pixi.lock exists, so the
+        # lock has to satisfy the pixi that reads it.  Pin the version: an unpinned
+        # setup-pixi takes the latest release, and a pixi that wants a newer lock
+        # FORMAT re-solves to upgrade it, which --locked forbids -- CI then fails on
+        # a lock whose contents are perfectly current.  That is what broke #51.
+        # Bump this together with pixi.lock, never on its own.
+        pixi-version: v0.79.0
     - name: Lint with flake8
       run: |
         # stop the build if there are Python syntax errors or undefined names
@@ -37,7 +45,7 @@ jobs:
       run: |
         pixi run coverage
     - name: Archive code coverage results
-      uses: actions/upload-artifact@v4
+      uses: actions/upload-artifact@v6
       with:
         name: code-coverage-report-${{ matrix.os }}
         path: coverage.xml

.gitignore

@@ -43,6 +43,7 @@ htmlcov/
 .coverage.*
 .cache
 nosetests.xml
+pytest.xml
 coverage.xml
 *.cover
 .hypothesis/