Process completed with exit code 4.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-backend ^14.0 -> satisfiable by typo3/cms-backend[v14.0.2, v14.1.0, v14.1.1]. - typo3/cms-backend v14.0.2 requires typo3/cms-core 14.0.2 -> found typo3/cms-core[v14.0.2] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.0 requires typo3/cms-core 14.1.0 -> found typo3/cms-core[v14.1.0] but it conflicts with your root composer.json require (^12.0 || ^13.0). - typo3/cms-backend v14.1.1 requires typo3/cms-core 14.1.1 -> found typo3/cms-core[v14.1.1] but it conflicts with your root composer.json require (^12.0 || ^13.0). Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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@0400d5f644dc74513175e3cd8d07132dd4860809. 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/