Process completed with exit code 2.

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

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires esign/laravel-underscore-translatable ^1.6 -> satisfiable by esign/laravel-underscore-translatable[1.6.0, 1.7.0]. - Root composer.json requires orchestra/testbench 11.* -> satisfiable by orchestra/testbench[v11.0.0, 11.x-dev]. - esign/laravel-underscore-translatable 1.6.0 requires illuminate/support ^7.0|^8.0|^9.0|^10.0|^11.0 -> satisfiable by illuminate/support[v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev]. - esign/laravel-underscore-translatable 1.7.0 requires illuminate/support ^10.0|^11.0|^12.0 -> satisfiable by illuminate/support[v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. - orchestra/canvas[v11.0.0, ..., 11.x-dev] require orchestra/canvas-core ^11.0.0 -> satisfiable by orchestra/canvas-core[v11.0.0, 11.x-dev]. - orchestra/canvas-core[v11.0.0, ..., 11.x-dev] require illuminate/support ^13.0 -> satisfiable by illuminate/support[v13.0.0, 13.0.x-dev (alias of dev-master), 13.x-dev], laravel/framework[v13.0.0, 13.0.x-dev (alias of dev-master), 13.x-dev]. - orchestra/testbench[v11.0.0, ..., 11.x-dev] require orchestra/workbench ^11.0.0 -> satisfiable by orchestra/workbench[v11.0.0, 11.x-dev]. - orchestra/workbench[v11.0.0, ..., 11.x-dev] require orchestra/canvas ^11.0.0 -> satisfiable by orchestra/canvas[v11.0.0, 11.x-dev]. - Conclusion: don't install illuminate/support v10.0.0 (conflict analysis result) - Conclusion: don't install illuminate/support v10.17.0 (conflict analysis result) - Conclusion: don't install illuminate/support v10.24.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.0.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.34.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.41.1 (conflict analysis result) - Conclusion: don't install illuminate/support v12.0.0 (conflict analysis result) - Conclusion: don't install illuminate/support v12.23.0 (conflict analysis result) - Conclusion: don't install illuminate/support v12.26.1 (conflict analysis result) - Conclusion: don't install illuminate/support v12.26.4 (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. - laravel/framework 13.0.x-dev is an alias of laravel/framework dev-master and thus requires it to be installed too. - Only one of these can be installed: illuminate/support[dev-master, v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev, v13.0.0, 13.0.x-dev, 13.x-dev], laravel/framework[dev-master, v13.0.0, 13.x-dev]. They all replace spatie/once and thus cannot coexist.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires esign/laravel-underscore-translatable ^1.6 -> satisfiable by esign/laravel-underscore-translatable[1.6.0, 1.7.0]. - Root composer.json requires orchestra/testbench 11.* -> satisfiable by orchestra/testbench[v11.0.0, 11.x-dev]. - esign/laravel-underscore-translatable 1.6.0 requires illuminate/support ^7.0|^8.0|^9.0|^10.0|^11.0 -> satisfiable by illuminate/support[v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev]. - esign/laravel-underscore-translatable 1.7.0 requires illuminate/support ^10.0|^11.0|^12.0 -> satisfiable by illuminate/support[v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev, v12.0.0, ..., 12.x-dev]. - Conclusion: don't install illuminate/support v10.16.1 (conflict analysis result) - Conclusion: don't install illuminate/support v10.49.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.33.2 (conflict analysis result) - Conclusion: don't install illuminate/support v11.41.0 (conflict analysis result) - Conclusion: don't install illuminate/support v11.50.0 (conflict analysis result) - Conclusion: don't install illuminate/support v12.22.1 (conflict analysis result) - Conclusion: don't install illuminate/support v12.26.0 (conflict analysis result) - Conclusion: don't install illuminate/support v12.26.3 (conflict analysis result) - Conclusion: don't install illuminate/support v12.41.1 (conflict analysis result) - Conclusion: don't install illuminate/support v12.55.0 (conflict analysis result)

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

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

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

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

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

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

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

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

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

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

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

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

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

The operation was canceled.

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

The operation was canceled.

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

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

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

The operation was canceled.

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

The operation was canceled.

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

The operation was canceled.

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

A task was canceled.

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

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

The operation was canceled.

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

The operation was canceled.

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

The operation was canceled.

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

The operation was canceled.

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

A task was canceled.

The strategy configuration was canceled because "test.ubuntu-latest_8_3_13____2" 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. 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@v2. 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@v2. 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@v2. 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@v2. 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@v2. 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@v2. 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@v2. 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/