Hi,
Has anyone upgrade to 2.4.3 successfully?
I tried I’m getting the following issues:
Problem 1 - Root composer.json requires dealerdirect/phpcodesniffer-composer-installer ^0.5.0 → satisfiable by dealerdirect/phpcodesniffer-composer-installer[v0.5.0]. - dealerdirect/phpcodesniffer-composer-installer v0.5.0 requires composer-plugin-api ^1.0 → found composer-plugin-api[2.1.0] but it does not match the constraint. Problem 2 - Root composer.json requires magento/magento2-functional-testing-framework ^3.0 → satisfiable by magento/magento2-functional-testing-framework[3.0.0, …, 3.7.0]. - allure-framework/allure-codeception[1.4.3, …, 1.4.4] require allure-framework/allure-php-api ~1.1.8 → satisfiable by allure-framework/allure-php-api[1.1.8]. - Conclusion: don’t install allure-framework/allure-php-api[1.1.8] | install one of ramsey/uuid[3.9.6, 4.1.3] (conflict analysis result) - Conclusion: don’t install magento/magento2-functional-testing-framework[3.4.0] | install one of ramsey/uuid[3.9.6, 4.1.3], allure-framework/allure-codeception[1.4.5] (conflict analysis result) - Conclusion: don’t install ramsey/uuid[3.9.6] | install ramsey/uuid[4.1.3] (conflict analysis result) - Conclusion: don’t install ramsey/uuid[4.1.3] | install one of magento/magento2-functional-testing-framework[3.6.0, 3.6.1, 3.7.0] (conflict analysis result) - Conclusion: don’t install magento/magento2-functional-testing-framework 3.6.0 (conflict analysis result) - Conclusion: don’t install magento/magento2-functional-testing-framework 3.6.1 (conflict analysis result) - Conclusion: don’t install magento/magento2-functional-testing-framework 3.7.0 (conflict analysis result) - allure-framework/allure-codeception 1.4.5 requires allure-framework/allure-php-api ~1.2.1 → satisfiable by allure-framework/allure-php-api[1.2.1]. - Conclusion: don’t install allure-framework/allure-php-api 1.2.1 (conflict analysis result) - Root composer.json requires allure-framework/allure-phpunit ~1.2.0 → satisfiable by allure-framework/allure-phpunit[1.2.0, …, 1.2.4]. - Conclusion: don’t install ramsey/uuid[4.1.1] | install one of allure-framework/allure-php-api[1.1.0, …, 1.1.8] (conflict analysis result) - You can only install one version of a package, so only one of these can be installed: allure-framework/allure-php-api[1.1.0, …, 1.3.1]. - allure-framework/allure-codeception 1.4.2 requires allure-framework/allure-php-api ~1.1.7 → satisfiable by allure-framework/allure-php-api[1.1.7, 1.1.8]. - Conclusion: install one of magento/magento2-functional-testing-framework[3.4.0, 3.6.0, 3.6.1], allure-framework/allure-codeception[1.4.2, 1.4.3, 1.4.4] (conflict analysis result) - Root composer.json requires magento/product-community-edition 2.4.3 → satisfiable by magento/product-community-edition[2.4.3]. - magento/product-community-edition 2.4.3 requires ramsey/uuid ~4.1.0 → satisfiable by ramsey/uuid[4.1.0, 4.1.1, 4.1.2, 4.1.3]. - Conclusion: don’t install ramsey/uuid[4.1.2] | install one of allure-framework/allure-php-api[1.1.0, …, 1.1.8] (conflict analysis result) - allure-framework/allure-php-api 1.1.7 requires ramsey/uuid ^3.0 → satisfiable by ramsey/uuid[3.0.0, …, 3.9.6]. - Only one of these can be installed: rhumsaa/uuid[2.7.0, …, 2.8.2], ramsey/uuid[3.0.0, …, 3.9.6, 4.0.0, …, 4.2.3]. ramsey/uuid replaces rhumsaa/uuid and thus cannot coexist with it. - Conclusion: don’t install ramsey/uuid[3.9.5] | install one of ramsey/uuid[4.1.2, 4.1.3] (conflict analysis result) Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Can anyone help please?