doctrine/dbal 2.5.13 composer json
"require": {
"php": ">=5.3.2",
"doctrine/common": ">=2.4,<2.8-dev"
}
resolves to doctrine/common 2.7.3.
doctrine/common 2.7.3 composer json
"require": {
"php": "~5.6|~7.0",
"doctrine/inflector": "1.*",
"doctrine/cache": "1.*",
"doctrine/collections": "1.*",
"doctrine/lexer": "1.*",
"doctrine/annotations": "1.*"
}
resolves to doctrine/annotations 1.5.0
doctrine/annotations 1.5.0 requires PHP 7:
This release increments the minimum supported PHP version to 7.1.0
Please see http://doctrine-project.org/2017/07/25/php-7.1-requirement-and-composer.html
Closing as invalid
@Ocramius Yes, I see the link. It states that dbal 2.6.0 drops support for PHP 5.
But dbal 2.5.13 has also inadvertently dropped support for PHP 5.6, because doctrine/[email protected] requires doctrine/[email protected], which requires PHP 7.1.
@gwagroves no, the composer SAT system will simply exclude those dependencies when running composer update, since they aren't compatible with your environment.
Ah, OK. Good to know. Unfortunately we have to commit the dependencies, and composer update was run under 7.1, but the server runs 5.6.
Thanks!
@gwagroves eh, never ever ever ever ever do that: please run updates in a production-alike environment.
Most helpful comment
@gwagroves eh, never ever ever ever ever do that: please run updates in a production-alike environment.