Composer platform requirement conflicts during installation
25K reputation · 08 Jun 2026, 23:10 UTC
Platform Requirement Parity
Composer utilizes the composer.lock file to ensure environment parity by prioritizing locked versions over composer.json constraints during the install command. To prevent runtime failures, Composer validates that the local PHP version and installed extensions meet the requirements defined by the dependency graph.
Conflict Resolution Behavior
A challenge arises when multiple dependencies in a project specify conflicting minimum platform requirements. While the --ignore-platform-reqs flag can bypass these checks to allow the installation to proceed, this does not resolve the underlying version mismatch.
What is the documented behavior for resolving conflicting minimum PHP version requirements across multiple dependencies during a standard install? Does Composer prioritize the highest minimum version required by any single package, or is there a specific resolution logic for overlapping platform constraints?