-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to install Magento with Composer version 2.4.4 #36516
Comments
Hi @fredden. Thank you for your report.
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket. ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Hi @engcom-November. Thank you for working on this issue.
|
✅ Jira issue https://jira.corp.adobe.com/browse/AC-7102 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-November. Thank you for verifying the issue. |
Is duplicate of #36515 😉 |
Preconditions and environment
2.4-develop
branch, after 4b43b2bSteps to reproduce
composer install
Expected result
Required packages are installed.
Actual result
An error is shown.
Additional information
The
laminas/laminas-dependency-plugin
package does not support recent / current versions of Composer. See laminas/laminas-dependency-plugin@54d508a for some details about this. It's likely that this plug-in can be safely removed from this project.Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: