Weekly global Tool Linting and Tests #715
mvdbeekci.yaml
on: schedule
Matrix: Setup cache and determine changed repositories
Matrix: Test tools
Matrix: Lint tool-list
Matrix: Combine chunked test results
Annotations
2 errors and 39 warnings
|
Lint tool-list (3.11)
Process completed with exit code 1.
|
|
Test tools (24, 3.11)
The job has exceeded the maximum execution time of 6h0m0s
|
|
Test tools (13, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (12, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (9, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (25, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (3, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (16, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (18, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (1, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (6, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (5, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (4, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (39, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (10, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (29, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (17, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (14, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (15, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (33, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (8, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (27, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (20, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (22, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (21, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (7, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (26, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (31, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (19, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (30, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (23, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (0, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (37, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (28, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (38, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (36, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (34, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (2, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (35, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (11, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test tools (32, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SimenB/github-actions-cpu-cores@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Tool linting output
|
617 KB |
sha256:d3d169e51999f117553cbb84f68020804e74a5c62496e5acce70e6e567c41cc4
|
|
|
Tool test output 0
|
639 KB |
sha256:20fa96447c53ff1930da130027af6e888e9c3e49a1d54a6f5d91f67f0b684fcf
|
|
|
Tool test output 1
|
217 KB |
sha256:e36bb85a7cae06b81b0a022d520a8d014a905d31fef039636ec0ee654062c457
|
|
|
Tool test output 10
|
335 KB |
sha256:cd60fdad7b19d0c29a0d01af5721b7d5d1d6975fdbf4df57367e79ea5ad16fe3
|
|
|
Tool test output 11
|
734 KB |
sha256:53454ad02922144bffe8008c74493a5f1d3a8dc10ff675f56b142e8a48b0e619
|
|
|
Tool test output 12
|
139 KB |
sha256:4579e28372a721864d256db98031cd1adca8b63fd312be11087fdf443badcd37
|
|
|
Tool test output 13
|
108 KB |
sha256:7b9290dab6a49728f8f05ad414722561c3fb09776b644ab0222faf9d0c039941
|
|
|
Tool test output 14
|
287 KB |
sha256:ae9bb538a6878b33e20d3bcc4118682dbac9ebf9bf741dae5a2cf6bafbd407b3
|
|
|
Tool test output 15
|
358 KB |
sha256:6722dd934c7c07d5a9cf272b76838a82f482604117203424108ea105baad003e
|
|
|
Tool test output 16
|
391 KB |
sha256:55796e621b0991c10019e4511130514c0574bea74062fe749c3f7de105a01e36
|
|
|
Tool test output 17
|
280 KB |
sha256:2c82d377a06f8fc4688acc36dadb89613993ebc3101780228f5f66e84c3df95d
|
|
|
Tool test output 18
|
393 KB |
sha256:1db56253fc7cee3b05a19ac74ac12dd8faaf4927db4873a8f68ecc1ebb1cccf8
|
|
|
Tool test output 19
|
378 KB |
sha256:01ece9dad9ae215e31bf9ee9366b85a6718ad39eefe25e7031271bd637a26304
|
|
|
Tool test output 2
|
253 KB |
sha256:2f98dd0f803496b49d55686e687580f0fd16d3a6d179d474793847fbed11ab64
|
|
|
Tool test output 20
|
641 KB |
sha256:62459cf92ba3b9b32bd3efef1f8d21f67e66a4a785f5c52d3729172679e01753
|
|
|
Tool test output 21
|
409 KB |
sha256:5992b1246d1b061e8e6650d3ee9ee8a8a88e2459158f539df594074f1d932fb1
|
|
|
Tool test output 22
|
385 KB |
sha256:d7efd45ff6ab719934ab653e20556ba10519c44c254280f9467f0fb69b011c25
|
|
|
Tool test output 23
|
710 KB |
sha256:fcb9340f16b4f4c83b08a25654c8705c74956b03f0e19b95b06503c2ca81551f
|
|
|
Tool test output 25
|
253 KB |
sha256:a3c189dfd22ff0d0ee23280a20c1d38413b96f715a50b24e7571b99ef17f7587
|
|
|
Tool test output 26
|
493 KB |
sha256:a90f3651466d8268334698e615d5ef898c621f5a25590f7b5dc9a67bd6fa4d60
|
|
|
Tool test output 27
|
1.01 MB |
sha256:e2c2b94d67cb73cc6a6dc66ce5e358a9d252d4aa79a6da06bfd64b427bb4b41b
|
|
|
Tool test output 28
|
460 KB |
sha256:91a4bb6aeeeacbf5bcd3f92ceb65f71decaee929e792ba0d3dd444a925462153
|
|
|
Tool test output 29
|
256 KB |
sha256:5b955a8d106b78246a5ecf1d06e9043bfd07fffa2c0ba383cfa2ac5f294a3043
|
|
|
Tool test output 3
|
200 KB |
sha256:f3bdef1ab091562fc3a9d84aba68cc08ebbdabdd5c9e8e06c236bb081c20a3ae
|
|
|
Tool test output 30
|
266 KB |
sha256:4c76a5340467c5419f274e77ff9a5b70926a3ba7a18853229fecc82aea87e0b7
|
|
|
Tool test output 31
|
635 KB |
sha256:55e901e31f019da8ddb3fb2cfb92a649bc56ac5131f3035b96afaebfb364d961
|
|
|
Tool test output 32
|
452 KB |
sha256:826d93aa756191eb5eb389aec718dc58d8f7022eed83e68192c5df427e686603
|
|
|
Tool test output 33
|
274 KB |
sha256:43dc309347920b48c1f9952a8efc367e20b77482a681abc1076f28b1cfc77deb
|
|
|
Tool test output 34
|
407 KB |
sha256:86d8b9d518a84b9c878b1e7e732f7bed6acefc66abaf4c55ff497e0700c5f7c3
|
|
|
Tool test output 35
|
1.49 MB |
sha256:e1db396baaab03951537c18f0f30b641a9a691895f66c8ad87bbdbc2407a8b2f
|
|
|
Tool test output 36
|
837 KB |
sha256:6c3964a9c9eca4fb7cda0b43f801486950c9b9295c90b8e2aa7b81cfa79f7e62
|
|
|
Tool test output 37
|
433 KB |
sha256:ec36cc4693ab201575d84cd5f6586740a0e0ad45b0dea705a322900dd8c45cee
|
|
|
Tool test output 38
|
667 KB |
sha256:e3687fa5c28eb43215c10397f981b32d836ffeaaf6fe1935f7d0b88ba73d2779
|
|
|
Tool test output 39
|
371 KB |
sha256:05fc7879f1ccb4477aa55c2f1805d724124d825a4857e6e54adc891f363e4020
|
|
|
Tool test output 4
|
367 KB |
sha256:0f984f71d0c868aa2bc73210e7cd01a7b5011f0c068cff40ffd5b65d399aa9b7
|
|
|
Tool test output 5
|
364 KB |
sha256:45e80f27ca19247493a72e7027475dc61bb85e2d84c6daec500998698e79a704
|
|
|
Tool test output 6
|
185 KB |
sha256:d56ea98affb5c410463bde583fe8d21fd4582c64fb60b61a28e894cf65ff4bfa
|
|
|
Tool test output 7
|
514 KB |
sha256:aedadaedc2f950bd397ba80d797720b3818a7e3c7d1bb5bb210229b13e5f110b
|
|
|
Tool test output 8
|
410 KB |
sha256:2936c0a28292873abc671cb7120b64ebca833640c0c0698d1fcc535b38ac7d49
|
|
|
Tool test output 9
|
366 KB |
sha256:4560708a0cb5cf849939a2a573d1365edc5d64edb60983f8e6f52b42742dace3
|
|