As mentioned in the title, it would be useful to (temporarily) add "conflict": {"phpunit/php-code-coverage": ">9.2.17"} to the constraints of this package.
The reason: coverage report became massively unreliable for the purposes of mutation testing starting with phpunit/php-code-coverage:9.2.18, as reported by @kukulich and acknowledged by @Slamdunk in sebastianbergmann/php-code-coverage#953
This is only a temporary measure: @Slamdunk has been talking with me about it, and he's hard at work on it in sebastianbergmann/php-code-coverage#964, which should fix the problem, but which may take more time to land.
At this moment, many mutation test suites keep going red due to invalid reduced coverage (some packages were even at 100%, and need constant adjustments when composer.lock gets changed).
Therefore, it would be healthy to declare an incompatibility in a new minor release, for now.
Sorry if this puts more load on your end :-(
As mentioned in the title, it would be useful to (temporarily) add
"conflict": {"phpunit/php-code-coverage": ">9.2.17"}to the constraints of this package.The reason: coverage report became massively unreliable for the purposes of mutation testing starting with
phpunit/php-code-coverage:9.2.18, as reported by @kukulich and acknowledged by @Slamdunk in sebastianbergmann/php-code-coverage#953This is only a temporary measure: @Slamdunk has been talking with me about it, and he's hard at work on it in sebastianbergmann/php-code-coverage#964, which should fix the problem, but which may take more time to land.
At this moment, many mutation test suites keep going red due to invalid reduced coverage (some packages were even at 100%, and need constant adjustments when
composer.lockgets changed).Therefore, it would be healthy to declare an incompatibility in a new minor release, for now.
Sorry if this puts more load on your end :-(