fix: remove ParaTest installation steps to resolve PHP 8.1 dependency conflicts #1062
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.
Previous commits attempted to install ParaTest v7.3.1 explicitly to work around dependency issues, but this caused conflicts with Pest's requirements. The root
composer.jsonrequirespestphp/pest ^2.8.0, which requiresbrianium/paratest ^7.4.0. However,brianium/paratest ^7.4.0requires PHP 8.2+, creating an impossible dependency situation for PHP 8.1.Changes
composer update -oRoot Cause
The manual ParaTest installation approach caused dependency conflicts:
pestphp/pest ^2.8.0requiresbrianium/paratest ^7.4.0brianium/paratest ^7.4.0requires PHP 8.2+brianium/paratest:~7.3.1conflicts with Pest's requirementsSolution
By removing the manual ParaTest installation steps and letting Composer handle dependency resolution automatically, the workflow can now successfully install compatible versions for all PHP versions (8.1, 8.2, 8.3) without conflicts.
Before/After
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.