Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest ^2.0 -> satisfiable by pestphp/pest[v2.0.1, ..., 2.x-dev]. - brianium/paratest[v7.9.0, ..., v7.11.2] require php ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.12.0, ..., 7.x-dev] require php ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.0, ..., v7.5.7] require php ~8.2.0 || ~8.3.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.8, ..., v7.8.4] require php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.8.5, ..., 7.8.x-dev] require php ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - pestphp/pest v2.33.3 requires brianium/paratest ^7.4.0 -> satisfiable by brianium/paratest[v7.4.0, ..., 7.x-dev]. - pestphp/pest v2.33.5 requires brianium/paratest ^7.4.1 -> satisfiable by brianium/paratest[v7.4.1, ..., 7.x-dev]. - pestphp/pest v2.34.3 requires brianium/paratest ^7.4.3 -> satisfiable by brianium/paratest[v7.4.3, ..., 7.x-dev]. - pestphp/pest v2.36.0 conflicts with phpunit/phpunit 10.5.63. - pestphp/pest v2.36.0 conflicts with phpunit/phpunit 10.5.62. - pestphp/pest v2.36.0 conflicts with phpunit/phpunit 10.5.x-dev. - pestphp/pest v2.36.0 requires phpunit/phpunit ^10.5.36 -> satisfiable by phpunit/phpunit[10.5.62, 10.5.63, 10.5.x-dev]. - pestphp/pest[v2.36.1, ..., 2.x-dev] require php ^8.2.0 -> your php version (8.1.34) does not satisfy that requirement. - Conclusion: don't install pestphp/pest v2.0.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.0.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.1.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.3.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.4.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.7.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.5 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.13.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.14.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.16.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.16.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.18.0

The strategy configuration was canceled because "test.ubuntu-latest_8_1_10___pr" 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 pestphp/pest-plugin-laravel ^2.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.0.0, ..., 2.x-dev]. - brianium/paratest[v7.9.0, ..., v7.11.2] require php ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.12.0, ..., 7.x-dev] require php ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.0, ..., v7.5.7] require php ~8.2.0 || ~8.3.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.4.8, ..., v7.8.4] require php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.1.34) does not satisfy that requirement. - brianium/paratest[v7.8.5, ..., 7.8.x-dev] require php ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0 -> your php version (8.1.34) does not satisfy that requirement. - pestphp/pest v2.0.1 conflicts with phpunit/phpunit 10.5.63. - pestphp/pest v2.0.1 conflicts with phpunit/phpunit 10.5.x-dev. - pestphp/pest v2.0.1 requires phpunit/phpunit ^10.0.16 -> satisfiable by phpunit/phpunit[10.5.62, 10.5.63, 10.5.x-dev]. - pestphp/pest v2.33.3 requires brianium/paratest ^7.4.0 -> satisfiable by brianium/paratest[v7.4.0, ..., 7.x-dev]. - pestphp/pest v2.33.5 requires brianium/paratest ^7.4.1 -> satisfiable by brianium/paratest[v7.4.1, ..., 7.x-dev]. - pestphp/pest v2.34.3 requires brianium/paratest ^7.4.3 -> satisfiable by brianium/paratest[v7.4.3, ..., 7.x-dev]. - pestphp/pest[v2.36.1, ..., 2.x-dev] require php ^8.2.0 -> your php version (8.1.34) does not satisfy that requirement. - pestphp/pest-plugin-laravel v2.0.0 requires pestphp/pest ^2.0.0 -> satisfiable by pestphp/pest[v2.0.1, ..., 2.x-dev]. - pestphp/pest-plugin-laravel v2.1.0 requires pestphp/pest ^2.8.3 -> satisfiable by pestphp/pest[v2.8.3, ..., 2.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires pestphp/pest ^2.13.0 -> satisfiable by pestphp/pest[v2.13.0, ..., 2.x-dev]. - pestphp/pest-plugin-laravel v2.3.0 requires pestphp/pest ^2.33.6 -> satisfiable by pestphp/pest[v2.33.6, ..., 2.x-dev]. - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require pestphp/pest ^2.34.7 -> satisfiable by pestphp/pest[v2.34.7, ..., 2.x-dev]. - Conclusion: don't install pestphp/pest v2.0.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.1.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.2.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.3.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.4.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.5.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.6.3 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.7.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.1 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.8.2 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.9.4 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.11.0 (conflict analysis result) - Conclusion: don't install pestphp/pest v2.12.0 (conflict analysis result) - Concl

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

The operation was canceled.

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

The operation was canceled.

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

The operation was canceled.

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

The operation was canceled.

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

The operation was canceled.

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

The operation was canceled.

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