Fix php-compatibility constrains #1
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description copied from dlopez-akalam#1
Recently, in the develop branch of phpcompatibility/php-compatibility has been removed the support for squizlabs/php_codesniffer v3.x in favor of v4.x. PHPCompatibility/PHPCompatibility@93ef2b8
That is incompatible with metadrop/grumphp-php-compatibility, and also incompatible with drupal/coder. However, the release 10.0.0-alpha2 of phpcompatibility/php-compatibility still declares the compatibility with squizlabs/php_codesniffer 3.x.
Considering the date of this commit 516059d and comparing it with the releases of https://github.com/PHPCompatibility/PHPCompatibility/tags I'm changing the constraint so metadrop/grumphp-php-compatibility can continue being installed