Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires roave/backward-compatibility-check ^7 -> satisfiable by roave/backward-compatibility-check[7.0.0, ..., 7.4.0]. - roave/backward-compatibility-check[7.0.0, ..., 7.1.0] require php ~8.0.0 || ~8.1.0 -> your php version (8.5.4) does not satisfy that requirement. - roave/backward-compatibility-check[7.2.0, ..., 7.4.0] require php ~8.1.0 || ~8.2.0 -> your php version (8.5.4) does not satisfy that requirement.

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/console is locked to version v8.0.7 and an update of this package was not requested. - symfony/console v8.0.7 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 2 - symfony/event-dispatcher is locked to version v8.0.4 and an update of this package was not requested. - symfony/event-dispatcher v8.0.4 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 3 - symfony/finder is locked to version v8.0.6 and an update of this package was not requested. - symfony/finder v8.0.6 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 4 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 5 - doctrine/instantiator is locked to version 2.1.0 and an update of this package was not requested. - doctrine/instantiator 2.1.0 requires php ^8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 6 - consolidation/output-formatters is locked to version 4.7.1 and an update of this package was not requested. - consolidation/output-formatters 4.7.1 requires symfony/console ^4 || ^5 || ^6 || ^7 || ^8 -> satisfiable by symfony/console[v8.0.7]. - symfony/console v8.0.7 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement.

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

The operation was canceled.

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

The operation was canceled.

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

The operation was canceled.

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

The operation was canceled.

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