Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 10.* -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - Root composer.json requires nunomaduro/collision ^8.5.0 -> satisfiable by nunomaduro/collision[v8.5.0, ..., v8.x-dev]. - nunomaduro/collision[v8.5.0, ..., v8.x-dev] conflict with laravel/framework 10.x-dev. - Conclusion: don't install laravel/framework v10.48.29 (conflict analysis result) - Conclusion: don't install laravel/framework v10.49.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.49.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.50.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.50.1 (conflict analysis result) - Conclusion: don't install laravel/framework 10.50.2 (conflict analysis result)

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

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

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

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

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

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

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

The strategy configuration was canceled because "test.ubuntu-latest_8_2_10____2" 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 laravel/framework 10.* -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - Root composer.json requires nunomaduro/collision ^8.5.0 -> satisfiable by nunomaduro/collision[v8.5.0, ..., v8.x-dev]. - nunomaduro/collision[v8.5.0, ..., v8.x-dev] conflict with laravel/framework 10.x-dev. - Conclusion: don't install laravel/framework v10.48.29 (conflict analysis result) - Conclusion: don't install laravel/framework v10.49.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.49.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.50.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.50.1 (conflict analysis result) - Conclusion: don't install laravel/framework 10.50.2 (conflict analysis result)

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

The operation was canceled.

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

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 10.* -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - Root composer.json requires nunomaduro/collision ^8.5.0 -> satisfiable by nunomaduro/collision[v8.5.0, ..., v8.x-dev]. - nunomaduro/collision[v8.5.0, ..., v8.x-dev] conflict with laravel/framework 10.x-dev. - Conclusion: don't install laravel/framework v10.48.29 (conflict analysis result) - Conclusion: don't install laravel/framework v10.49.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.49.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.50.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.50.1 (conflict analysis result) - Conclusion: don't install laravel/framework 10.50.2 (conflict analysis result)

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

The operation was canceled.

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

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires laravel/framework 10.* -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - Root composer.json requires nunomaduro/collision ^8.5.0 -> satisfiable by nunomaduro/collision[v8.5.0, ..., v8.x-dev]. - nunomaduro/collision[v8.5.0, ..., v8.x-dev] conflict with laravel/framework 10.x-dev. - Conclusion: don't install laravel/framework v10.48.29 (conflict analysis result) - Conclusion: don't install laravel/framework v10.49.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.49.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.50.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.50.1 (conflict analysis result) - Conclusion: don't install laravel/framework 10.50.2 (conflict analysis result)

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 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/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/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/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/