-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Composer create-project doesn't check platform requirements #11697
Comments
The
Could that be the root issue? |
This would indeed explain why the |
What is there in the drupal/recommended-project template which would have resulted in that in composer.lock? |
It looks like it's in the Running |
Right, I'm guessing whatever builds the release sets I'm not sure what to do about this.. If the composer.json does not have the overrides anymore we probably could warn when running an install, just not sure how much work this would be. Really the best way would be to avoid shipping a lock file IMO and let dependency resolution happen at create-project time. |
My
composer.json
:...replace me...
Output of
composer diagnose
:When I run this command on PHP 8.2:
everything installs as expected. However, subsequent composer commands complain. E.g doing:
outputs:
Checking this package:
Shows that it was installed as part of the original create-project.
And I expected this to happen:
Don't install the project in the first place if a package won't work on the platform.
The text was updated successfully, but these errors were encountered: