Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php ^8.4 but your php version (8.3.31) does not satisfy that requirement. Problem 2 - Root composer.json requires infection/infection ^0.27 -> satisfiable by infection/infection[0.27.0, ..., 0.27.11]. - Root composer.json requires phpunit/phpunit ^11.4.2 -> satisfiable by phpunit/phpunit[11.5.50, ..., 11.5.55]. - infection/infection[0.27.0, ..., 0.27.9] require sebastian/diff ^3.0.2 || ^4.0 || ^5.0 -> satisfiable by sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1]. - infection/infection[0.27.10, ..., 0.27.11] require nikic/php-parser ^4.15.1 -> satisfiable by nikic/php-parser[v4.15.1, ..., v4.19.5]. - phpunit/php-code-coverage 11.0.12 requires nikic/php-parser ^5.7.0 -> satisfiable by nikic/php-parser[v5.7.0]. - phpunit/phpunit[11.5.51, ..., 11.5.55] require phpunit/php-code-coverage ^11.0.12 -> satisfiable by phpunit/php-code-coverage[11.0.12]. - phpunit/phpunit[11.5.51, ..., 11.5.55] require sebastian/diff ^6.0.2 -> satisfiable by sebastian/diff[6.0.2]. - sebastian/diff 3.0.2 requires php ^7.1 -> your php version (8.3.31) does not satisfy that requirement. - sebastian/diff[4.0.0, ..., 4.0.1] require php ^7.3 -> your php version (8.3.31) does not satisfy that requirement. - Conclusion: don't install phpunit/phpunit 11.5.50 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: nikic/php-parser[v4.15.1, ..., v4.19.5, v5.0.0, ..., v5.7.0]. - You can only install one version of a package, so only one of these can be installed: sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1, 6.0.0, 6.0.1, 6.0.2]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php ^8.4 but your php version (8.2.31) does not satisfy that requirement. Problem 2 - Root composer.json requires infection/infection ^0.27 -> satisfiable by infection/infection[0.27.0, ..., 0.27.11]. - Root composer.json requires phpunit/phpunit ^11.4.2 -> satisfiable by phpunit/phpunit[11.5.50, ..., 11.5.55]. - infection/infection[0.27.10, ..., 0.27.11] require nikic/php-parser ^4.15.1 -> satisfiable by nikic/php-parser[v4.15.1, ..., v4.19.5]. - infection/infection[0.27.0, ..., 0.27.9] require sebastian/diff ^3.0.2 || ^4.0 || ^5.0 -> satisfiable by sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1]. - phpunit/php-code-coverage 11.0.12 requires nikic/php-parser ^5.7.0 -> satisfiable by nikic/php-parser[v5.7.0]. - phpunit/phpunit 11.5.50 requires phpunit/php-code-coverage ^11.0.12 -> satisfiable by phpunit/php-code-coverage[11.0.12]. - phpunit/phpunit 11.5.50 requires sebastian/diff ^6.0.2 -> satisfiable by sebastian/diff[6.0.2]. - sebastian/diff 3.0.2 requires php ^7.1 -> your php version (8.2.31) does not satisfy that requirement. - sebastian/diff[4.0.0, ..., 4.0.1] require php ^7.3 -> your php version (8.2.31) does not satisfy that requirement. - Conclusion: don't install phpunit/phpunit 11.5.55 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: nikic/php-parser[v4.15.1, ..., v4.19.5, v5.0.0, ..., v5.7.0]. - You can only install one version of a package, so only one of these can be installed: sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1, 6.0.0, 6.0.1, 6.0.2]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires infection/infection ^0.27 -> satisfiable by infection/infection[0.27.0, ..., 0.27.11]. - Root composer.json requires phpunit/phpunit ^11.4.2 -> satisfiable by phpunit/phpunit[11.5.50, ..., 11.5.55]. - infection/infection[0.27.10, ..., 0.27.11] require nikic/php-parser ^4.15.1 -> satisfiable by nikic/php-parser[v4.15.1, ..., v4.19.5]. - infection/infection[0.27.0, ..., 0.27.9] require sebastian/diff ^3.0.2 || ^4.0 || ^5.0 -> satisfiable by sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1]. - phpunit/php-code-coverage 11.0.12 requires nikic/php-parser ^5.7.0 -> satisfiable by nikic/php-parser[v5.7.0]. - phpunit/phpunit 11.5.50 requires phpunit/php-code-coverage ^11.0.12 -> satisfiable by phpunit/php-code-coverage[11.0.12]. - phpunit/phpunit 11.5.50 requires sebastian/diff ^6.0.2 -> satisfiable by sebastian/diff[6.0.2]. - sebastian/diff 3.0.2 requires php ^7.1 -> your php version (8.4.21) does not satisfy that requirement. - sebastian/diff[4.0.0, ..., 4.0.1] require php ^7.3 -> your php version (8.4.21) does not satisfy that requirement. - Conclusion: don't install phpunit/phpunit 11.5.55 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: nikic/php-parser[v4.15.1, ..., v4.19.5, v5.0.0, ..., v5.7.0]. - You can only install one version of a package, so only one of these can be installed: sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1, 6.0.0, 6.0.1, 6.0.2]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php ^8.4 but your php version (8.2.31) does not satisfy that requirement. Problem 2 - Root composer.json requires infection/infection ^0.27 -> satisfiable by infection/infection[0.27.0, ..., 0.27.11]. - Root composer.json requires phpunit/phpunit ^11.4.2 -> satisfiable by phpunit/phpunit[11.5.50, ..., 11.5.55]. - infection/infection[0.27.0, ..., 0.27.9] require sebastian/diff ^3.0.2 || ^4.0 || ^5.0 -> satisfiable by sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1]. - infection/infection[0.27.10, ..., 0.27.11] require nikic/php-parser ^4.15.1 -> satisfiable by nikic/php-parser[v4.15.1, ..., v4.19.5]. - phpunit/php-code-coverage 11.0.12 requires nikic/php-parser ^5.7.0 -> satisfiable by nikic/php-parser[v5.7.0]. - phpunit/phpunit[11.5.51, ..., 11.5.55] require phpunit/php-code-coverage ^11.0.12 -> satisfiable by phpunit/php-code-coverage[11.0.12]. - phpunit/phpunit[11.5.51, ..., 11.5.55] require sebastian/diff ^6.0.2 -> satisfiable by sebastian/diff[6.0.2]. - sebastian/diff 3.0.2 requires php ^7.1 -> your php version (8.2.31) does not satisfy that requirement. - sebastian/diff[4.0.0, ..., 4.0.1] require php ^7.3 -> your php version (8.2.31) does not satisfy that requirement. - Conclusion: don't install phpunit/phpunit 11.5.50 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: nikic/php-parser[v4.15.1, ..., v4.19.5, v5.0.0, ..., v5.7.0]. - You can only install one version of a package, so only one of these can be installed: sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1, 6.0.0, 6.0.1, 6.0.2]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires infection/infection ^0.27 -> satisfiable by infection/infection[0.27.0, ..., 0.27.11]. - Root composer.json requires phpunit/phpunit ^11.4.2 -> satisfiable by phpunit/phpunit[11.5.50, ..., 11.5.55]. - infection/infection[0.27.0, ..., 0.27.9] require sebastian/diff ^3.0.2 || ^4.0 || ^5.0 -> satisfiable by sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1]. - infection/infection[0.27.10, ..., 0.27.11] require nikic/php-parser ^4.15.1 -> satisfiable by nikic/php-parser[v4.15.1, ..., v4.19.5]. - phpunit/php-code-coverage 11.0.12 requires nikic/php-parser ^5.7.0 -> satisfiable by nikic/php-parser[v5.7.0]. - phpunit/phpunit[11.5.51, ..., 11.5.55] require phpunit/php-code-coverage ^11.0.12 -> satisfiable by phpunit/php-code-coverage[11.0.12]. - phpunit/phpunit[11.5.51, ..., 11.5.55] require sebastian/diff ^6.0.2 -> satisfiable by sebastian/diff[6.0.2]. - sebastian/diff 3.0.2 requires php ^7.1 -> your php version (8.4.21) does not satisfy that requirement. - sebastian/diff[4.0.0, ..., 4.0.1] require php ^7.3 -> your php version (8.4.21) does not satisfy that requirement. - Conclusion: don't install phpunit/phpunit 11.5.50 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: nikic/php-parser[v4.15.1, ..., v4.19.5, v5.0.0, ..., v5.7.0]. - You can only install one version of a package, so only one of these can be installed: sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1, 6.0.0, 6.0.1, 6.0.2]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php ^8.4 but your php version (8.3.31) does not satisfy that requirement. Problem 2 - Root composer.json requires infection/infection ^0.27 -> satisfiable by infection/infection[0.27.0, ..., 0.27.11]. - Root composer.json requires phpunit/phpunit ^11.4.2 -> satisfiable by phpunit/phpunit[11.5.50, ..., 11.5.55]. - infection/infection[0.27.10, ..., 0.27.11] require nikic/php-parser ^4.15.1 -> satisfiable by nikic/php-parser[v4.15.1, ..., v4.19.5]. - infection/infection[0.27.0, ..., 0.27.9] require sebastian/diff ^3.0.2 || ^4.0 || ^5.0 -> satisfiable by sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1]. - phpunit/php-code-coverage 11.0.12 requires nikic/php-parser ^5.7.0 -> satisfiable by nikic/php-parser[v5.7.0]. - phpunit/phpunit 11.5.50 requires phpunit/php-code-coverage ^11.0.12 -> satisfiable by phpunit/php-code-coverage[11.0.12]. - phpunit/phpunit 11.5.50 requires sebastian/diff ^6.0.2 -> satisfiable by sebastian/diff[6.0.2]. - sebastian/diff 3.0.2 requires php ^7.1 -> your php version (8.3.31) does not satisfy that requirement. - sebastian/diff[4.0.0, ..., 4.0.1] require php ^7.3 -> your php version (8.3.31) does not satisfy that requirement. - Conclusion: don't install phpunit/phpunit 11.5.55 (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: nikic/php-parser[v4.15.1, ..., v4.19.5, v5.0.0, ..., v5.7.0]. - You can only install one version of a package, so only one of these can be installed: sebastian/diff[3.0.2, ..., 3.0.6, 4.0.0, ..., 4.0.6, 5.0.0, ..., 5.1.1, 6.0.0, 6.0.1, 6.0.2]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

The operation was canceled.

The operation was canceled.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

The operation was canceled.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

The operation was canceled.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

The operation was canceled.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_prefer-" failed

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026