Avoid node warnings

.github/workflows/build_wheels.yml

@@ -60,7 +60,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v4
 
     - name: Build sdist
       env:
@@ -90,20 +90,20 @@ jobs:
 
     steps:
 
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
 
       # Get Python 3.12 x32 and x64 on Windows. (As of 2023-10-12 these are not
       # always available by default.)
       #
       - name: Install Python 3.12 x32 on Windows.
         if: runner.os == 'Windows'
-        uses: actions/setup-python@v2
+        uses: actions/setup-python@v5
         with:
           python-version: '3.12'
           architecture: x86
       - name: Install Python 3.12 x64 on Windows.
         if: runner.os == 'Windows'
-        uses: actions/setup-python@v2
+        uses: actions/setup-python@v5
         with:
           python-version: '3.12'
 
@@ -115,7 +115,7 @@ jobs:
       # `python-config3` return settings for Python-3.12, instead of for
       # whatever Python is being used by cibuildwheel.
       #
-      - uses: actions/setup-python@v2
+      - uses: actions/setup-python@v5
 
       # On Linux, get qemu so we can build for aarch64.
       #

.github/workflows/cla.yml

@@ -12,7 +12,7 @@ jobs:
       - name: "CLA Assistant"
         if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target'
         # Beta Release
-        uses: contributor-assistant/github-action@v2.2.0
+        uses: contributor-assistant/github-action@v2.4.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           # the below token should have repo scope and must be manually added by you in the repository's secret

.github/workflows/test-valgrind.yml

@@ -19,8 +19,8 @@ jobs:
 
     steps:
 
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v2
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
 
       - name: test_mupdf-master-branch
         env:

.github/workflows/test_mupdf-master-branch.yml

@@ -21,8 +21,8 @@ jobs:
 
     steps:
 
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v2
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
 
       - name: test_mupdf-master-branch
         env:

.github/workflows/test_mupdf-release-branch.yml

@@ -22,8 +22,8 @@ jobs:
 
     steps:
 
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v2
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
 
       - name: test_mupdf-release-branch
         env:

.github/workflows/test_pyodide.yml

@@ -29,9 +29,9 @@ jobs:
 
     steps:
 
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
 
-      - uses: actions/setup-python@v4
+      - uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
 

.github/workflows/test_quick.yml

@@ -22,8 +22,8 @@ jobs:
 
     steps:
 
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v2
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
 
       - name: test_quick
 

.github/workflows/test_sysinstall.yml

@@ -16,7 +16,7 @@ jobs:
 
     steps:
 
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
 
       # It seems to be important not to install a custom python here,
       # because `sudo` (which we need to use when installing to /usr/local
@@ -25,7 +25,7 @@ jobs:
       # pymupdf files being installed into .../python3.11/site-packages and
       # .../python3.10/site-packages, and tests all fail to import pymupdf.
       #
-      #- uses: actions/setup-python@v2
+      #- uses: actions/setup-python@v5
         #with:
         #  # 3.12 doesn't have setuptools. As of 2024-01-03, MuPDF build requires setuptools before it
         #  # sees `--venv` and defers to a venv, so we currently have to force use of python 3.11.

scripts/sysinstall.py

@@ -14,7 +14,7 @@
 Note that we run some commands with sudo; it's important that these use the
 same python as non-sudo, otherwise things can be build and installed for
 different python versions. For example when we are run from a github action, it
-should not do `- uses: actions/setup-python@v2` but instead use whatever system
+should not do `- uses: actions/setup-python@v5` but instead use whatever system
 python is already defined.
 
 Args: