Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires illuminate/support ^13.0 -> satisfiable by illuminate/support[v13.0.0, ..., 13.x-dev], laravel/framework[v13.0.0, ..., 13.x-dev]. - Root composer.json requires pestphp/pest-plugin-laravel ^2.0|^3.1 -> satisfiable by pestphp/pest-plugin-laravel[v2.0.0, ..., 2.x-dev, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.0.0 requires laravel/framework ^10.4.1 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - pestphp/pest-plugin-laravel v2.1.0 requires laravel/framework ^10.15.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev, v11.44.1, ..., 11.x-dev]. - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev, v11.44.1, ..., 11.x-dev]. - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev, v11.44.1, ..., 11.x-dev]. - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> satisfiable by laravel/framework[v11.44.1, ..., 11.x-dev, v12.1.1, ..., 12.x-dev]. - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> satisfiable by laravel/framework[v11.44.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev]. - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> satisfiable by laravel/framework[v11.44.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev]. - Conclusion: don't install laravel/framework 13.x-dev (conflict analysis result) - Conclusion: don't install laravel/framework v13.0.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.1.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.1.1 (conflict analysis result) - Conclusion: don't install laravel/framework v13.2.0 (conflict analysis result) - Conclusion: don't install illuminate/support dev-master (conflict analysis result) - Conclusion: don't install illuminate/support v13.2.0 (conflict analysis result) - illuminate/support 13.0.x-dev is an alias of illuminate/support dev-master and thus requires it to be installed too. - Only one of these can be installed: illuminate/view[v9.0.0-beta.1, ..., 9.x-dev, v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev, v13.0.0, ..., 13.x-dev], laravel/framework[dev-master, 9.x-dev, v10.48.29, ..., 10.x-dev, v11.44.1, ..., 11.x-dev, v12.1.1, ..., 12.x-dev, v13.0.0, ..., 13.x-dev]. laravel/framework replaces illuminate/view and thus cannot coexist with it. - laravel/framework 13.0.x-dev is an alias of laravel/framework dev-master and thus requires it to be installed too.

The strategy configuration was canceled because "pest._13" failed

The operation was canceled.

The strategy configuration was canceled because "pest._13" failed

The operation was canceled.

The strategy configuration was canceled because "pest._13" 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@v2, EndBug/add-and-commit@v5. 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/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

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/