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/database ^11|^12|^13 -> satisfiable by illuminate/database[v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.61.1, v13.0.0, ..., v13.14.0], laravel/framework[v12.60.0, ..., v12.61.1, v13.10.0, ..., v13.14.0]. - Root composer.json requires illuminate/support 11.* -> satisfiable by illuminate/support[v11.0.0, ..., v11.51.0]. - Root composer.json requires orchestra/testbench ^9.6|^10.0|^11.0 -> satisfiable by orchestra/testbench[v9.6.0, ..., v9.17.0, v10.0.0, ..., v10.11.0, v11.0.0, v11.1.0]. - Conclusion: don't install laravel/framework v12.60.1 (conflict analysis result) - Conclusion: don't install laravel/framework v12.60.2 (conflict analysis result) - Conclusion: don't install laravel/framework v12.61.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.61.1 (conflict analysis result) - Conclusion: don't install laravel/framework v13.10.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.11.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.11.1 (conflict analysis result) - Conclusion: don't install laravel/framework v13.11.2 (conflict analysis result) - Conclusion: don't install laravel/framework v13.12.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.13.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.14.0 (conflict analysis result) - Conclusion: don't install illuminate/database v11.34.2 (conflict analysis result) - Conclusion: don't install illuminate/database v11.45.3 (conflict analysis result) - Conclusion: don't install illuminate/database v11.51.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.16.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.26.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.27.1 (conflict analysis result) - Conclusion: don't install illuminate/database v12.43.1 (conflict analysis result) - Conclusion: don't install illuminate/database v12.56.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.61.1 (conflict analysis result) - Conclusion: don't install illuminate/database v13.7.0 (conflict analysis result) - Conclusion: don't install illuminate/database v13.8.0 (conflict analysis result) - Conclusion: don't install illuminate/database v13.14.0 (conflict analysis result) - Only one of these can be installed: laravel/framework[v12.60.0, ..., v12.61.1, v13.10.0, ..., v13.14.0], illuminate/support[v11.0.0, ..., v11.51.0]. laravel/framework replaces illuminate/support and thus cannot coexist with it.

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/database ^11|^12|^13 -> satisfiable by illuminate/database[v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.61.1, v13.0.0, ..., v13.14.0], laravel/framework[v12.60.0, ..., v12.61.1, v13.10.0, ..., v13.14.0]. - Root composer.json requires illuminate/support 11.* -> satisfiable by illuminate/support[v11.0.0, ..., v11.51.0]. - Root composer.json requires orchestra/testbench ^9.6|^10.0|^11.0 -> satisfiable by orchestra/testbench[v9.6.0, ..., v9.17.0, v10.0.0, ..., v10.11.0, v11.0.0, v11.1.0]. - illuminate/database[v13.0.0, ..., v13.14.0] require php ^8.3 -> your php version (8.2.31) does not satisfy that requirement. - laravel/framework[v13.10.0, ..., v13.14.0] require php ^8.3 -> your php version (8.2.31) does not satisfy that requirement. - Conclusion: don't install laravel/framework v12.60.1 (conflict analysis result) - Conclusion: don't install laravel/framework v12.60.2 (conflict analysis result) - Conclusion: don't install laravel/framework v12.61.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.61.1 (conflict analysis result) - Conclusion: don't install illuminate/database v11.34.2 (conflict analysis result) - Conclusion: don't install illuminate/database v11.45.3 (conflict analysis result) - Conclusion: don't install illuminate/database v11.51.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.16.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.26.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.27.1 (conflict analysis result) - Conclusion: don't install illuminate/database v12.43.1 (conflict analysis result) - Conclusion: don't install illuminate/database v12.56.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.61.1 (conflict analysis result) - Only one of these can be installed: laravel/framework[v12.60.0, ..., v12.61.1, v13.10.0, ..., v13.14.0], illuminate/support[v11.0.0, ..., v11.51.0]. laravel/framework replaces illuminate/support and thus cannot coexist with it.

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/database ^11|^12|^13 -> satisfiable by illuminate/database[v11.0.0, ..., v11.51.0, v12.0.0, ..., v12.61.1, v13.0.0, ..., v13.14.0], laravel/framework[v12.60.0, ..., v12.61.1, v13.10.0, ..., v13.14.0]. - Root composer.json requires illuminate/support 11.* -> satisfiable by illuminate/support[v11.0.0, ..., v11.51.0]. - Root composer.json requires orchestra/testbench ^9.6|^10.0|^11.0 -> satisfiable by orchestra/testbench[v9.6.0, ..., v9.17.0, v10.0.0, ..., v10.11.0, v11.0.0, v11.1.0]. - Conclusion: don't install laravel/framework v12.60.1 (conflict analysis result) - Conclusion: don't install laravel/framework v12.60.2 (conflict analysis result) - Conclusion: don't install laravel/framework v12.61.0 (conflict analysis result) - Conclusion: don't install laravel/framework v12.61.1 (conflict analysis result) - Conclusion: don't install laravel/framework v13.10.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.11.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.11.1 (conflict analysis result) - Conclusion: don't install laravel/framework v13.11.2 (conflict analysis result) - Conclusion: don't install laravel/framework v13.12.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.13.0 (conflict analysis result) - Conclusion: don't install laravel/framework v13.14.0 (conflict analysis result) - Conclusion: don't install illuminate/database v11.34.2 (conflict analysis result) - Conclusion: don't install illuminate/database v11.45.3 (conflict analysis result) - Conclusion: don't install illuminate/database v11.51.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.16.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.26.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.27.1 (conflict analysis result) - Conclusion: don't install illuminate/database v12.43.1 (conflict analysis result) - Conclusion: don't install illuminate/database v12.56.0 (conflict analysis result) - Conclusion: don't install illuminate/database v12.61.1 (conflict analysis result) - Conclusion: don't install illuminate/database v13.7.0 (conflict analysis result) - Conclusion: don't install illuminate/database v13.8.0 (conflict analysis result) - Conclusion: don't install illuminate/database v13.14.0 (conflict analysis result) - Only one of these can be installed: laravel/framework[v12.60.0, ..., v12.61.1, v13.10.0, ..., v13.14.0], illuminate/support[v11.0.0, ..., v11.51.0]. laravel/framework replaces illuminate/support and thus cannot coexist with it.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/