Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires diglactic/laravel-breadcrumbs ^10.0 -> satisfiable by diglactic/laravel-breadcrumbs[v10.0.0]. - Root composer.json requires illuminate/support ^11.0 || ^12.0 -> satisfiable by illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. - Root composer.json requires javaabu/mediapicker ^1.0@dev -> satisfiable by javaabu/mediapicker[1.0.x-dev (alias of dev-main)]. - diglactic/laravel-breadcrumbs v10.0.0 requires laravel/framework ^10.0 || ^11.0 || ^12.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - illuminate/support[v12.0.0, ..., 12.x-dev] require nesbot/carbon ^3.8.4 -> found nesbot/carbon[dev-master, 3.8.4, ..., 3.x-dev (alias of dev-master)] but it conflicts with your root composer.json require (^2.63). - Conclusion: don't install illuminate/support v11.0.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.0.1 (conflict analysis result) - Conclusion: don't install illuminate/support v11.34.0 (conflict analysis result) - Only one of these can be installed: laravel/framework[v10.48.29, ..., 10.x-dev], illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. 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 diglactic/laravel-breadcrumbs ^10.0 -> satisfiable by diglactic/laravel-breadcrumbs[v10.0.0]. - Root composer.json requires illuminate/support ^11.0 || ^12.0 -> satisfiable by illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. - diglactic/laravel-breadcrumbs v10.0.0 requires laravel/framework ^10.0 || ^11.0 || ^12.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - illuminate/support[v12.0.0, ..., 12.x-dev] require nesbot/carbon ^3.8.4 -> found nesbot/carbon[dev-master, 3.8.4, ..., 3.x-dev (alias of dev-master)] but it conflicts with your root composer.json require (^2.63). - Conclusion: don't install illuminate/support v11.41.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.50.0 (conflict analysis result) - Only one of these can be installed: laravel/framework[v10.48.29, ..., 10.x-dev], illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. laravel/framework replaces illuminate/support and thus cannot coexist with it.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_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 diglactic/laravel-breadcrumbs ^10.0 -> satisfiable by diglactic/laravel-breadcrumbs[v10.0.0]. - Root composer.json requires illuminate/support ^11.0 || ^12.0 -> satisfiable by illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. - diglactic/laravel-breadcrumbs v10.0.0 requires laravel/framework ^10.0 || ^11.0 || ^12.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - illuminate/support[v12.0.0, ..., 12.x-dev] require nesbot/carbon ^3.8.4 -> found nesbot/carbon[dev-master, 3.8.4, ..., 3.x-dev (alias of dev-master)] but it conflicts with your root composer.json require (^2.63). - Conclusion: don't install illuminate/support v11.41.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.50.0 (conflict analysis result) - Only one of these can be installed: laravel/framework[v10.48.29, ..., 10.x-dev], illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. laravel/framework replaces illuminate/support and thus cannot coexist with it.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_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 diglactic/laravel-breadcrumbs ^10.0 -> satisfiable by diglactic/laravel-breadcrumbs[v10.0.0]. - Root composer.json requires illuminate/support ^11.0 || ^12.0 -> satisfiable by illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. - Root composer.json requires javaabu/mediapicker ^1.0@dev -> satisfiable by javaabu/mediapicker[1.0.x-dev (alias of dev-main)]. - diglactic/laravel-breadcrumbs v10.0.0 requires laravel/framework ^10.0 || ^11.0 || ^12.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - illuminate/support[v12.0.0, ..., 12.x-dev] require nesbot/carbon ^3.8.4 -> found nesbot/carbon[dev-master, 3.8.4, ..., 3.x-dev (alias of dev-master)] but it conflicts with your root composer.json require (^2.63). - Conclusion: don't install illuminate/support v11.0.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.0.1 (conflict analysis result) - Conclusion: don't install illuminate/support v11.34.0 (conflict analysis result) - Only one of these can be installed: laravel/framework[v10.48.29, ..., 10.x-dev], illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. laravel/framework replaces illuminate/support and thus cannot coexist with it.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires diglactic/laravel-breadcrumbs ^10.0 -> satisfiable by diglactic/laravel-breadcrumbs[v10.0.0]. - Root composer.json requires illuminate/support ^11.0 || ^12.0 -> satisfiable by illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. - diglactic/laravel-breadcrumbs v10.0.0 requires laravel/framework ^10.0 || ^11.0 || ^12.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - illuminate/support[v12.0.0, ..., 12.x-dev] require nesbot/carbon ^3.8.4 -> found nesbot/carbon[dev-master, 3.8.4, ..., 3.x-dev (alias of dev-master)] but it conflicts with your root composer.json require (^2.63). - Conclusion: don't install illuminate/support v11.41.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.50.0 (conflict analysis result) - Only one of these can be installed: laravel/framework[v10.48.29, ..., 10.x-dev], illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. laravel/framework replaces illuminate/support and thus cannot coexist with it.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires diglactic/laravel-breadcrumbs ^10.0 -> satisfiable by diglactic/laravel-breadcrumbs[v10.0.0]. - Root composer.json requires illuminate/support ^11.0 || ^12.0 -> satisfiable by illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. - Root composer.json requires javaabu/mediapicker ^1.0@dev -> satisfiable by javaabu/mediapicker[1.0.x-dev (alias of dev-main)]. - diglactic/laravel-breadcrumbs v10.0.0 requires laravel/framework ^10.0 || ^11.0 || ^12.0 -> satisfiable by laravel/framework[v10.48.29, ..., 10.x-dev]. - illuminate/support[v12.0.0, ..., 12.x-dev] require nesbot/carbon ^3.8.4 -> found nesbot/carbon[dev-master, 3.8.4, ..., 3.x-dev (alias of dev-master)] but it conflicts with your root composer.json require (^2.63). - Conclusion: don't install illuminate/support v11.0.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.0.1 (conflict analysis result) - Conclusion: don't install illuminate/support v11.34.0 (conflict analysis result) - Only one of these can be installed: laravel/framework[v10.48.29, ..., 10.x-dev], illuminate/support[v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. laravel/framework replaces illuminate/support and thus cannot coexist with it.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_10___pr" failed

The operation was canceled.

The strategy configuration was canceled because "tests.ubuntu-latest_8_3_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@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/

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/

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/

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/

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/