Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/console[v7.0.0, ..., v7.1.1] require php >=8.2 -> your php version (8.1.28) does not satisfy that requirement. - typo3/coding-standards 0.8.x-dev is an alias of typo3/coding-standards dev-main and thus requires it to be installed too. - typo3/testing-framework 8.0.9 requires typo3/cms-core 12.*.*@dev || 13.*.*@dev -> found typo3/cms-core[v12.0.0, ..., v12.4.15, v13.0.0, v13.0.1, v13.1.0, v13.1.1] but it conflicts with your temporary update constraint (typo3/cms-core:^11.5). - Root composer.json requires typo3/coding-standards ^0.8.0@dev -> satisfiable by typo3/coding-standards[v0.8.0, 0.8.x-dev (alias of dev-main)]. - typo3/testing-framework[7.0.2, ..., 7.0.4] require typo3/cms-core 11.*.*@dev || 12.*.*@dev -> satisfiable by typo3/cms-core[v11.5.0, ..., v11.5.37]. - typo3/cms-core[v11.5.5, ..., v11.5.37] require symfony/console ^5.4 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.3, ..., v11.5.4] require symfony/console ^5.3.7 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.0, ..., v11.5.2] require symfony/console ^5.3.0 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - You can only install one version of a package, so only one of these can be installed: symfony/console[v5.4.0, ..., v5.4.40, v6.0.0, ..., v6.4.8, v7.0.0, ..., v7.1.1]. - typo3/coding-standards dev-main requires symfony/console ^6.4 || ^7.0 -> satisfiable by symfony/console[v6.4.0, ..., v6.4.8, v7.0.0, ..., v7.1.1]. - Root composer.json requires typo3/testing-framework ^7.0.2 || ^8.0.9 -> satisfiable by typo3/testing-framework[7.0.2, 7.0.3, 7.0.4, 8.0.9]. 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/testing-framework 8.0.9 requires typo3/cms-core 12.*.*@dev || 13.*.*@dev -> found typo3/cms-core[v12.0.0, ..., v12.4.15, v13.0.0, v13.0.1, v13.1.0, v13.1.1] but it conflicts with your temporary update constraint (typo3/cms-core:^11.5). - Root composer.json requires typo3/coding-standards ^0.8.0@dev -> satisfiable by typo3/coding-standards[v0.8.0, 0.8.x-dev]. - Conclusion: don't install symfony/console v5.4.0 (conflict analysis result) - Root composer.json requires typo3/testing-framework ^7.0.2 || ^8.0.9 -> satisfiable by typo3/testing-framework[7.0.2, 7.0.3, 7.0.4, 8.0.9]. - typo3/testing-framework[7.0.2, ..., 7.0.4] require typo3/cms-core 11.*.*@dev || 12.*.*@dev -> satisfiable by typo3/cms-core[v11.5.0, ..., v11.5.37]. - typo3/cms-core[v11.5.5, ..., v11.5.37] require symfony/console ^5.4 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.3, ..., v11.5.4] require symfony/console ^5.3.7 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.0, ..., v11.5.2] require symfony/console ^5.3.0 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - Conclusion: don't install symfony/console v5.4.1 (conflict analysis result) 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/coding-standards 0.8.x-dev is an alias of typo3/coding-standards dev-main and thus requires it to be installed too. - typo3/testing-framework 8.0.9 requires typo3/cms-core 12.*.*@dev || 13.*.*@dev -> found typo3/cms-core[v12.0.0, ..., v12.4.15, v13.0.0, v13.0.1, v13.1.0, v13.1.1] but it conflicts with your temporary update constraint (typo3/cms-core:^11.5). - Root composer.json requires typo3/coding-standards ^0.8.0@dev -> satisfiable by typo3/coding-standards[v0.8.0, 0.8.x-dev (alias of dev-main)]. - Root composer.json requires typo3/testing-framework ^7.0.2 || ^8.0.9 -> satisfiable by typo3/testing-framework[7.0.2, 7.0.3, 7.0.4, 8.0.9]. - typo3/testing-framework[7.0.2, ..., 7.0.4] require typo3/cms-core 11.*.*@dev || 12.*.*@dev -> satisfiable by typo3/cms-core[v11.5.0, ..., v11.5.37]. - typo3/cms-core[v11.5.5, ..., v11.5.37] require symfony/console ^5.4 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.3, ..., v11.5.4] require symfony/console ^5.3.7 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.0, ..., v11.5.2] require symfony/console ^5.3.0 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - You can only install one version of a package, so only one of these can be installed: symfony/console[v5.4.0, ..., v5.4.40, v6.0.0, ..., v6.4.8, v7.0.0, ..., v7.1.1]. - typo3/coding-standards dev-main requires symfony/console ^6.4 || ^7.0 -> satisfiable by symfony/console[v6.4.0, ..., v6.4.8, v7.0.0, ..., v7.1.1]. - Conclusion: don't install symfony/console v7.1.1 (conflict analysis result) 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/testing-framework 8.0.9 requires typo3/cms-core 12.*.*@dev || 13.*.*@dev -> found typo3/cms-core[v12.0.0, ..., v12.4.15, v13.0.0, v13.0.1, v13.1.0, v13.1.1] but it conflicts with your temporary update constraint (typo3/cms-core:^11.5). - Root composer.json requires typo3/coding-standards ^0.8.0@dev -> satisfiable by typo3/coding-standards[v0.8.0, 0.8.x-dev]. - Conclusion: don't install symfony/console v5.4.0 (conflict analysis result) - Root composer.json requires typo3/testing-framework ^7.0.2 || ^8.0.9 -> satisfiable by typo3/testing-framework[7.0.2, 7.0.3, 7.0.4, 8.0.9]. - typo3/testing-framework[7.0.2, ..., 7.0.4] require typo3/cms-core 11.*.*@dev || 12.*.*@dev -> satisfiable by typo3/cms-core[v11.5.0, ..., v11.5.37]. - typo3/cms-core[v11.5.5, ..., v11.5.37] require symfony/console ^5.4 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.3, ..., v11.5.4] require symfony/console ^5.3.7 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.0, ..., v11.5.2] require symfony/console ^5.3.0 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - Conclusion: don't install symfony/console v5.4.1 (conflict analysis result) 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/coding-standards 0.8.x-dev is an alias of typo3/coding-standards dev-main and thus requires it to be installed too. - typo3/testing-framework 8.0.9 requires typo3/cms-core 12.*.*@dev || 13.*.*@dev -> found typo3/cms-core[v12.0.0, ..., v12.4.15, v13.0.0, v13.0.1, v13.1.0, v13.1.1] but it conflicts with your temporary update constraint (typo3/cms-core:^11.5). - Root composer.json requires typo3/coding-standards ^0.8.0@dev -> satisfiable by typo3/coding-standards[v0.8.0, 0.8.x-dev (alias of dev-main)]. - Root composer.json requires typo3/testing-framework ^7.0.2 || ^8.0.9 -> satisfiable by typo3/testing-framework[7.0.2, 7.0.3, 7.0.4, 8.0.9]. - typo3/testing-framework[7.0.2, ..., 7.0.4] require typo3/cms-core 11.*.*@dev || 12.*.*@dev -> satisfiable by typo3/cms-core[v11.5.0, ..., v11.5.37]. - typo3/cms-core[v11.5.5, ..., v11.5.37] require symfony/console ^5.4 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.3, ..., v11.5.4] require symfony/console ^5.3.7 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.0, ..., v11.5.2] require symfony/console ^5.3.0 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - You can only install one version of a package, so only one of these can be installed: symfony/console[v5.4.0, ..., v5.4.40, v6.0.0, ..., v6.4.8, v7.0.0, ..., v7.1.1]. - typo3/coding-standards dev-main requires symfony/console ^6.4 || ^7.0 -> satisfiable by symfony/console[v6.4.0, ..., v6.4.8, v7.0.0, ..., v7.1.1]. - Conclusion: don't install symfony/console v7.1.1 (conflict analysis result) 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 - symfony/console[v7.0.0, ..., v7.1.1] require php >=8.2 -> your php version (8.1.28) does not satisfy that requirement. - typo3/coding-standards[v0.8.0, ..., 0.8.x-dev] require symfony/console ^6.4 || ^7.0 -> satisfiable by symfony/console[v6.4.0, ..., v6.4.8, v7.0.0, ..., v7.1.1]. - typo3/testing-framework 8.0.9 requires typo3/cms-core 12.*.*@dev || 13.*.*@dev -> found typo3/cms-core[v12.0.0, ..., v12.4.15, v13.0.0, v13.0.1, v13.1.0, v13.1.1] but it conflicts with your temporary update constraint (typo3/cms-core:^11.5). - Root composer.json requires typo3/coding-standards ^0.8.0@dev -> satisfiable by typo3/coding-standards[v0.8.0, 0.8.x-dev]. - typo3/testing-framework[7.0.2, ..., 7.0.4] require typo3/cms-core 11.*.*@dev || 12.*.*@dev -> satisfiable by typo3/cms-core[v11.5.0, ..., v11.5.37]. - typo3/cms-core[v11.5.5, ..., v11.5.37] require symfony/console ^5.4 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.3, ..., v11.5.4] require symfony/console ^5.3.7 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - typo3/cms-core[v11.5.0, ..., v11.5.2] require symfony/console ^5.3.0 -> satisfiable by symfony/console[v5.4.0, ..., v5.4.40]. - You can only install one version of a package, so only one of these can be installed: symfony/console[v5.4.0, ..., v5.4.40, v6.0.0, ..., v6.4.8, v7.0.0, ..., v7.1.1]. - Root composer.json requires typo3/testing-framework ^7.0.2 || ^8.0.9 -> satisfiable by typo3/testing-framework[7.0.2, 7.0.3, 7.0.4, 8.0.9]. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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