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|^3.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.0.0, ..., 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.0.0 requires laravel/framework ^10.4.1 -> found laravel/framework[v10.4.1, ..., 10.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.1.0 requires laravel/framework ^10.15.0 -> found laravel/framework[v10.15.0, ..., 10.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" 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|^3.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.0.0, ..., 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.0.0 requires laravel/framework ^10.4.1 -> found laravel/framework[v10.4.1, ..., 10.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.1.0 requires laravel/framework ^10.15.0 -> found laravel/framework[v10.15.0, ..., 10.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" 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|^3.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.0.0, ..., 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.0.0 requires laravel/framework ^10.4.1 -> found laravel/framework[v10.4.1, ..., 10.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.1.0 requires laravel/framework ^10.15.0 -> found laravel/framework[v10.15.0, ..., 10.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" failed

The operation was canceled.

The strategy configuration was canceled because "tests._8_3_13___prefer-stable" 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/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/