You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use splitit/sdk in our Magento project, but when we upgrade Magento to 2.4.4, it still get the following error:
Problem 1
- Root composer.json requires magento/product-community-edition 2.4.4 -> satisfiable by magento/product-community-edition[2.4.4].
- Root composer.json requires splitit/sdk ^1.6 -> satisfiable by splitit/sdk[1.6.0, ..., 1.6.10].
- Conclusion: don't install guzzlehttp/guzzle 7.4.2 (conflict analysis result)
- magento/product-community-edition 2.4.4 requires magento/framework 103.0.4 -> satisfiable by magento/framework[103.0.4].
- splitit/sdk[1.6.0, ..., 1.6.10] require guzzlehttp/guzzle ^6.2 -> satisfiable by guzzlehttp/guzzle[6.2.0, ..., 6.5.5].
- You can only install one version of a package, so only one of these can be installed: guzzlehttp/guzzle[v1.0.3, v1.0.4, v2.0.0, ..., v2.8.8, v3.0.0, ..., v3.8.1, 4.0.0, ..., 4.2.4, 5.0.0, ..., 5.3.4, 6.0.0, ..., 6.5.5, 7.0.0, ..., 7.4.2].
- magento/framework 103.0.4 requires guzzlehttp/guzzle ^7.3.0 -> satisfiable by guzzlehttp/guzzle[7.3.0, 7.4.0, 7.4.1, 7.4.2].
- Conclusion: don't install guzzlehttp/guzzle 7.4.0 (conflict analysis result)
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Magento 2.4.4 depends on guzzlehttp/guzzle 7.*, but this extension use guzzlehttp/guzzle ^6.2, could you update it?
The text was updated successfully, but these errors were encountered:
winds1983
changed the title
Could you change guzzlehttp/guzzle to >=7.4.2?
Could you change guzzlehttp/guzzle to 7.*?
Mar 30, 2022
We use splitit/sdk in our Magento project, but when we upgrade Magento to 2.4.4, it still get the following error:
Magento 2.4.4 depends on guzzlehttp/guzzle 7.*, but this extension use guzzlehttp/guzzle ^6.2, could you update it?
The text was updated successfully, but these errors were encountered: