Your requirements could not be resolved to an installable set of packages. Problem 1 - typo3/minimal v11.0.0 requires typo3/cms-backend ^11.0 -> found typo3/cms-backend[v11.0.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.1.0 requires typo3/cms-backend ^11.1 -> found typo3/cms-backend[v11.1.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.2.0 requires typo3/cms-backend ^11.2 -> found typo3/cms-backend[v11.2.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.3.0 requires typo3/cms-backend ^11.3 -> found typo3/cms-backend[v11.3.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.4.0 requires typo3/cms-backend ^11.4 -> found typo3/cms-backend[v11.4.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.5.0 requires typo3/cms-backend ^11.5 -> found typo3/cms-backend[v11.5.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - Root composer.json requires typo3/minimal ^11 -> satisfiable by typo3/minimal[v11.0.0, ..., v11.5.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 - typo3/minimal v12.0.0 requires typo3/cms-backend ^12.0 -> found typo3/cms-backend[v12.0.0, ..., v12.4.15] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v12.4.0 requires typo3/cms-backend ^12.4 -> found typo3/cms-backend[v12.4.0, ..., v12.4.15] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - Root composer.json requires typo3/minimal ^12 -> satisfiable by typo3/minimal[v12.0.0, v12.4.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 - typo3/cms-core is locked to version v13.0.1 and an update of this package was not requested. - typo3/cms-core v13.0.1 requires php ^8.2 -> your php version (8.1.28) does not satisfy that requirement. Problem 2 - symfony/dotenv v7.0.7 requires php >=8.2 -> your php version (8.1.28) does not satisfy that requirement. - helhum/dotenv-connector v3.1.0 requires symfony/dotenv ^5.1 || ^6.4 || ^7.0 -> satisfiable by symfony/dotenv[v7.0.7]. - helhum/dotenv-connector is locked to version v3.1.0 and an update of this package was not requested.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - typo3/cms-core is locked to version v13.0.1 and an update of this package was not requested. - typo3/cms-core v13.0.1 requires php ^8.2 -> your php version (8.1.28) does not satisfy that requirement. Problem 2 - symfony/dotenv v7.0.7 requires php >=8.2 -> your php version (8.1.28) does not satisfy that requirement. - helhum/dotenv-connector v3.1.0 requires symfony/dotenv ^5.1 || ^6.4 || ^7.0 -> satisfiable by symfony/dotenv[v7.0.7]. - helhum/dotenv-connector is locked to version v3.1.0 and an update of this package was not requested.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - typo3/minimal v12.0.0 requires typo3/cms-backend ^12.0 -> found typo3/cms-backend[v12.0.0, ..., v12.4.15] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v12.4.0 requires typo3/cms-backend ^12.4 -> found typo3/cms-backend[v12.4.0, ..., v12.4.15] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - Root composer.json requires typo3/minimal ^12 -> satisfiable by typo3/minimal[v12.0.0, v12.4.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 - typo3/minimal v11.0.0 requires typo3/cms-backend ^11.0 -> found typo3/cms-backend[v11.0.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.1.0 requires typo3/cms-backend ^11.1 -> found typo3/cms-backend[v11.1.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.2.0 requires typo3/cms-backend ^11.2 -> found typo3/cms-backend[v11.2.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.3.0 requires typo3/cms-backend ^11.3 -> found typo3/cms-backend[v11.3.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.4.0 requires typo3/cms-backend ^11.4 -> found typo3/cms-backend[v11.4.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - typo3/minimal v11.5.0 requires typo3/cms-backend ^11.5 -> found typo3/cms-backend[v11.5.0, ..., v11.5.37] but the package is fixed to v13.0.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - Root composer.json requires typo3/minimal ^11 -> satisfiable by typo3/minimal[v11.0.0, ..., v11.5.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 - typo3/cms-core is locked to version v13.0.1 and an update of this package was not requested. - typo3/cms-core v13.0.1 requires php ^8.2 -> your php version (8.1.28) does not satisfy that requirement. Problem 2 - symfony/dotenv v7.0.7 requires php >=8.2 -> your php version (8.1.28) does not satisfy that requirement. - helhum/dotenv-connector v3.1.0 requires symfony/dotenv ^5.1 || ^6.4 || ^7.0 -> satisfiable by symfony/dotenv[v7.0.7]. - helhum/dotenv-connector is locked to version v3.1.0 and an update of this package was not requested.

Process completed with exit code 2.

Process completed with exit code 1.

Process completed with exit code 1.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.