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 of the Change
It's advantageous that
composer.lock
is commited to the repository. This introduces more consistency when dependencies are installed by individuals for projects depending on WP_Mock.If someone wants to learn more about why this is important (if you have a better article, please post in comment!):
One notable update since #167 is maybe bumping PhpUnit to the
^9.5
constraint -- however the previous constraint>=7.0
made it so that9.5.x
could have been installed too.I've also removed
sebastian/comparator
from dev dependencies. Not sure what this is used for since I couldn't find any reference to it. Maybe it was required in older phpunit versions?As for
behat
andphp-coveralls
we might still use those later on.Closes #153
How to test the Change
Changelog Entry
composer.lock
is commited to gitChecklist: