Update first-party GitHub Actions to avoid warnings about node20

Details:
 * Update actions/checkout from v4 to v6
 * Update actions/setup-python from v5 to v6

https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Author: RytoEX

.github/workflows/all-lints.yml

@@ -25,7 +25,7 @@ jobs:
             python-version: 3.10
 
     steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@v6
     - uses: ./
       with:
         python-root-list: "./tests/*.py ./tests/subtest/*.py"

.github/workflows/test-python-install.yml

@@ -14,11 +14,11 @@ jobs:
     env:
       python-test-package: python-dummy
     steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@v6
 
     - name: Install Python if required
       if: ${{ matrix.use-external-python }}
-      uses: actions/setup-python@v5
+      uses: actions/setup-python@v6
       with:
         python-version: ${{ matrix.python-version }}
 

README.md

@@ -32,15 +32,15 @@ Basic:
 
 ```yml
 steps:
-  - uses: actions/checkout@v4
+  - uses: actions/checkout@v6
   - uses: marian-code/python-lint-annotate@v4
 ```
 
 Options:
 
 ```yml
 steps:
-  - uses: actions/checkout@v4
+  - uses: actions/checkout@v6
   - uses: marian-code/python-lint-annotate@v4
     with:
       python-root-list: "src/ tests/*"  # accepts wildcards
@@ -56,17 +56,17 @@ steps:
 
 ## Details
 
-Uses `actions/setup-python@v5`. Only python `3.8` - `3.12` versions are tested.
+Uses `actions/setup-python@v6`. Only python `3.8` - `3.12` versions are tested.
 Python `3.x` versions prior to `3.8` are not tested since they are EOL now.
 Any python `2.x` versions are unsupported! You can lint on Linux, Windows and MacOS.
 
 The linter versions are defined in [requirements.txt](requirements.txt).
 
 ## IMPORTANT - test environment
 
-The python version is set by `actions/setup-python@v5` using composite actions. This
+The python version is set by `actions/setup-python@v6` using composite actions. This
 means that the the action will change python you might have previously set with
-`actions/setup-python@v5`. There are two ways to circumvent this.
+`actions/setup-python@v6`. There are two ways to circumvent this.
 
 - Keep the lintnig action separated from others
 - Use it at the and of your workflow when the change in python version will not
@@ -84,8 +84,8 @@ jobs:
     name: Lint Python
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v4
-    - uses: actions/setup-python@v5
+    - uses: actions/checkout@v6
+    - uses: actions/setup-python@v6
       with:
         python-version: 3.9
     - run: |

action.yml

@@ -87,7 +87,7 @@ runs:
   steps:
     - name: Setup python
       if: ${{ ! inputs.use-external-python }}
-      uses: actions/setup-python@v5
+      uses: actions/setup-python@v6
       with:
         python-version: ${{ inputs.python-version }}
         architecture: x64

examples/actions-only_changed_files.yml

@@ -8,11 +8,11 @@ jobs:
     name: Lint
     steps:
       - name: Check out source repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0  # This is necessary to get the commits
       - name: Set up Python environment
-        uses: actions/setup-python@v5
+        uses: actions/setup-python@v6
         with:
           python-version: "3.8"
       - name: Get changed python files between base and head