Terminable Loop Command 1.3.1
Another day, another patch that allows Symfony 8! This time, no change to the package was necessary, apart from adapting a small stub used in the tests.
This is the full changelog:
- Add support for Symfony 8 (#50)
Another day, another patch that allows Symfony 8! This time, no change to the package was necessary, apart from adapting a small stub used in the tests.
This is the full changelog:
This small new patch was triggered by a PR from a new contributor, Kocal, thank you! The fixes needed to make Paraunit compatible with Symfony 8 was a single line change (plus some more in the unit tests), which is impressive since now we support 5 different major versions, all across from 4.4 (which is EOL) up to 8.0!
This small patch includes the same fix that I released with 2.1.0, a new timeout message that MySQL 8.0.24+ spits out under PHP 8.4. Many thanks to @ackermannd for reporting it and helping me in the process. It is also now tested against PHP 8.5 (but it didn’t require any changes).
This minor release includes a small refactoring that I did months ago (and didn’t release yet) where I bumped the minimum required PHP version to 8.1. This allowed me to do some clean up (mainly thanks to Rector) and fix multiple PHP deprecations. Attached to this, I’ve also released a fix that intercepts a new timeout message that MySQL 8.0.24+ spits out under PHP 8.4. Many thanks to @ackermannd for reporting it and helping me in the process.
It is also now tested against PHP 8.5 (but it didn’t require any changes).
This new release includes a couple of improvements: the first one is the addition of PHPUnit deprecation as separate test issues, so that those will be reported in a separate category, as with PHPUnit itself; the second one stems from some issues detected by PHP-CS-Fixer under PHP 8.5, where some skipped tests were marked erroneously as “abnormal terminations”. I discovered that, when using the requires attribute, PHPUnit would report only a Skipped event, without the TestStarted, TestPrepared and TestFinished events, which would trigger this issue.