Weekly global Tool Linting and Tests #720
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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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 (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/
|
|
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 (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 (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 (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 (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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Tool linting output
|
410 KB |
sha256:3c2292fd4a75f6e2518e09f5acf34248030ecb3b0dc762484551afae3beba54e
|
|
|
Tool test output 0
|
641 KB |
sha256:af9b46331f9086ef9966e39946d5d4ccd0e07f4055254de40c71cbe921106fe2
|
|
|
Tool test output 1
|
219 KB |
sha256:3112b113de060ea6d8fbef90872a4e55369db16763f5168735317b823afab7b3
|
|
|
Tool test output 10
|
335 KB |
sha256:1a7ea8946a6684010a69412ee57f251c4253a97197ddb377abb7a4d18abc4f7c
|
|
|
Tool test output 11
|
745 KB |
sha256:f1fab652e39401996b4a89032bce28c4db7be1308ea3387a0d7762bea16ecfc0
|
|
|
Tool test output 12
|
126 KB |
sha256:c6acb6d1ef3b74d8b97860ac763c6e6054c6d1840cc59e7d409e2330287a1fa6
|
|
|
Tool test output 13
|
109 KB |
sha256:6f7f46ea94a4ad110b3ce5250b09777255e48b6347aa886f3e2a1afd150eaee5
|
|
|
Tool test output 14
|
343 KB |
sha256:751c0a97872c96661bc5ac1c43034854d6357ccf2ce0a6eecab69a576aa1eb4a
|
|
|
Tool test output 15
|
332 KB |
sha256:83a8875bc6c165115260adaa1a5dbc364410b60c987cecfd65a7a2ff3b874967
|
|
|
Tool test output 16
|
357 KB |
sha256:ad25fc73a73187751a21ec2800923deececd6209ce44ff8b14ff4d5a6edfbe21
|
|
|
Tool test output 17
|
279 KB |
sha256:b13fbb54c45ee18e7faa6cae065f672ed12f4ab1344f660e6ed23913ce470ed8
|
|
|
Tool test output 18
|
397 KB |
sha256:cc8ba0534d84fedcacda4e0a6936e348ed6f92fcfbdf318293d0086c05223808
|
|
|
Tool test output 19
|
506 KB |
sha256:abdfc2ad055abeac50b79914b65bf2a4529efe17cc03b7864088cb8dbf5fb079
|
|
|
Tool test output 2
|
253 KB |
sha256:f8a516dbb643b7b65f1190a55994fa90f3bf809f3c898ef3fe2b2bcfe4d9500a
|
|
|
Tool test output 20
|
528 KB |
sha256:be8e13fa0b2007066d91948d2bcafe8bb8e512c8cbdb46ab3f6e911673908690
|
|
|
Tool test output 21
|
405 KB |
sha256:079abccbdfab883c77bf6584e1976eba21f56882cc0c6807ef123d99cfa11c19
|
|
|
Tool test output 22
|
384 KB |
sha256:54a95974ff3e1aaf75ba3fbf2774f92e945d110be2b06fb3e9f09b626123edc7
|
|
|
Tool test output 23
|
663 KB |
sha256:58468b3aee0bfd2edfd5aef54b5088fe1b73aa55fea7d6b8e35b9fba394eac41
|
|
|
Tool test output 25
|
254 KB |
sha256:129fb85ca0cd903719dede0c0f9c229d680f1042dc4a43414a23213818600007
|
|
|
Tool test output 26
|
501 KB |
sha256:224dfe34e6d393edc758330b10eb01c0e133f5c85a63699f72bfcb6487841cfd
|
|
|
Tool test output 27
|
1.01 MB |
sha256:80a6b1dce571aeb985232e7164d800f7eb5df4340352ee3125b6891244c90055
|
|
|
Tool test output 28
|
476 KB |
sha256:a4fc6766a43087d75cdef2ce30f5719fcccd347ca64a0f686e77b2c17e331452
|
|
|
Tool test output 29
|
246 KB |
sha256:85dd6936dc12c194ec1c35ebe57ad1b1c036349791ea5ed5da9391194c3102fa
|
|
|
Tool test output 3
|
201 KB |
sha256:f4e48c3ab8a1468e54e795965f16665d6ad03b6c528a479767b908c5cd5e656a
|
|
|
Tool test output 30
|
305 KB |
sha256:a52439e0cd42bdfe05907ca5add9477211e00f9ccfa02ee8f4175cd57d6a05ee
|
|
|
Tool test output 31
|
595 KB |
sha256:9e11ef4a0c829bec8af97d366160d707aa892d4771b2eed85fe151bc4473719e
|
|
|
Tool test output 32
|
494 KB |
sha256:29e002a46b8632adb3dcb494bcc147dd8560e01ea0319cdf98c19619701c2197
|
|
|
Tool test output 33
|
282 KB |
sha256:f01ece7cc5ebad02a0ef0efeeb44234e5c5ff41ae1ebf34dba6dce3c4c5bd2bc
|
|
|
Tool test output 34
|
398 KB |
sha256:b6002f7e8ec2d8d68a95330e8d28924932efa6e00cdd3a38ab7ab2a7cc1d6e57
|
|
|
Tool test output 35
|
1.48 MB |
sha256:d6ab4ac2e1f6847dfd5a3cf6fb803fd84e012eb41f953f5c178e0abcb735ead5
|
|
|
Tool test output 36
|
864 KB |
sha256:eb6e32e2bae674172d0bd1968ccc9a512686fd8ee32a4e4e6a391f5c8da8871a
|
|
|
Tool test output 37
|
440 KB |
sha256:1da1f6f5fcbdd8d7b4ceaa9a72ab0b036651e2687e693993d0bfc777c01dc280
|
|
|
Tool test output 38
|
668 KB |
sha256:b1e07c7a89629b8a0b8e6edc13d171f6dcbcacad177cec7b74acc4adf00441a2
|
|
|
Tool test output 39
|
371 KB |
sha256:a0ec9175ab925256108429a8983b74ab6163a410da2eb810395e6f92531a5070
|
|
|
Tool test output 4
|
373 KB |
sha256:3931a90684ec0f026775926b486e39bc91f0390e4b4ab8ca8bbed2408219ca82
|
|
|
Tool test output 5
|
332 KB |
sha256:23ae8231985306e1fabdfc2c1ebeda385130a7a52962c82c0fd7e51bdfda486e
|
|
|
Tool test output 6
|
175 KB |
sha256:c615530c040d21faca590705c2d7cb3c0a082be955443779f14b1455107a7736
|
|
|
Tool test output 7
|
527 KB |
sha256:0b95e36b9593a4b509a4e4a94d31db72b71f823bb411e69668035cbda1795dc2
|
|
|
Tool test output 8
|
443 KB |
sha256:60f88a67ab4d3acb2ffa218f8f96e9e9703792a14697283da20d0d974b951951
|
|
|
Tool test output 9
|
367 KB |
sha256:5b6eae9bb0d0ed8ecd0e5e3929941a81e834799ceaf5dfdcade9d1774f2c89c9
|
|