Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Process completed with exit code 1.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Foreach overwrites $internalError with its value variable.

Comparison operation ">" between int<1, max> and 0 is always true.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Comparison operation "<" between 1 and 1 is always false.

Offset 'message' on non-empty-array<mixed> on left side of ?? always exists and is always null.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Strict comparison using === between int<1, max> and 0 will always evaluate to false.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

No files were found with the provided path: baseline-php-8.5.neon. No artifacts will be uploaded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

No files were found with the provided path: baseline-php-8.2.neon. No artifacts will be uploaded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

No files were found with the provided path: baseline-php-8.4.neon. No artifacts will be uploaded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

No files were found with the provided path: baseline-php-8.3.neon. No artifacts will be uploaded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

No files were found with the provided path: baseline-php-8.5.neon. No artifacts will be uploaded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

No files were found with the provided path: baseline-php-8.4.neon. No artifacts will be uploaded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

No files were found with the provided path: baseline-php-8.3.neon. No artifacts will be uploaded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

No files were found with the provided path: baseline-php-8.2.neon. No artifacts will be uploaded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/