Paraunit

I may have jumped the gun while releasing the PHPUnit 11 compat, and I didn’t check that the CI was actually installing it. Unfortunately there were multiple dependencies still conflicting with it, and Prophecy needed some PRs to be compatible. I filed them and used them in my CI, so that now the compatibility is checked.

I needed to do multiple changes to make the CI green, but still no code changes was needed, only a widening of composer.json constraints and some tests & CI fixes.

On the same day of PHPUnit 11.0.0 release, I’m able to release a minor version of Paraunit that supports it, and no code change was necessary! You may still be impacted by PHPUnit’s breaking changes and require to adjust your tests accordingly, but Paraunit can be upgraded before with no hassle (provided that you have at least PHPUnit 10.5.4 already installed), since it’s cross-compatible between the two major versions.

This is a small patch to smooth the compatibility with the new release of PHPUnit, 10.4. Previous versions would still work fine, but I took the time to fix all the tests (that were broken due to reliance on @internal code such as PHPUnit events) and to add support for the new CLI options regarding the errors baseline.

This another small patch is to allow using Paraunit with Symfony 7, which was released just yesterday. The related PR needed just to fix a couple of return types. Paraunit should work flawlessly with PHP 8.3 too, which was released a couple of day prior, but I had to revert the additional CI job because Prophecy is not ready yet.

I discovered this bug while trying to upgrade a work project to PHPUnit 10. The issue was caused by an empty data provider.