Bumps phpunit/phpunit from 9.2.6 to 9.3.8.
Changelog
Sourced from phpunit/phpunit's changelog.
<h2>[9.3.8] - 2020-08-27</h2> <h3>Fixed</h3><h2>[9.3.7] - 2020-08-11</h2> <h3>Fixed</h3>
- #3937: Risky tests are inconsistently reported in JUnit XML
- #4435: Global assert wrappers break preloading
<h2>[9.3.6] - 2020-08-11</h2> <h3>Fixed</h3>
- #4419:
--migrate-configurationcannot migrate XML configuration files with multiple<exclude>elements- #4422: Error when
libxml_disable_entity_loader()is used in a data provider<h2>[9.3.5] - 2020-08-10</h2> <h3>Fixed</h3>
- #4417: Default value for
<coverage includeUncoveredFiles="true|false">XML configuration attribute wasfalseinstead oftrue<h2>[9.3.4] - 2020-08-10</h2> <h3>Added</h3>
- #4412: Code Coverage does not work for isolated test when PHAR is used
<h3>Fixed</h3>
- Added
--coverage-cache <directory>CLI option for enabling a cache for static analysis results; it will write its files to<directory>- Added
<coverage cacheDirectory="directory">XML configuration attribute for enabling a cache for static analysis results; it will write its files todirectory- Added
--warm-coverage-cacheCLI option for warming the cache for static analysis results; the cache must be configured for this to work<h2>[9.3.3] - 2020-08-08</h2> <h3>Changed</h3>
- #4405: Location for (current version of) XML Schema for XML configuration file has changed
- Default value for
<phpunit cacheResult="true|false">XML configuration attribute wasfalseinstead oftrue<h3>Fixed</h3>
- Reverted the workaround for #4399 now that the root cause is fixed in PHP-Scoper
Commits
Prepare release93d78d8Fix: Regenerate psalm baselined5be908Fix: Regenerate global assert wrappera404c34Fix: invalid reference in generate-global-assert-wrappers.phpd4480faRevert34f20ce794571f, hoping this makes the tests ...Update ChangeLogd723457Trim contents of <error>, <failure>, etc. elements7a2cfddUse PHP_EOL794571fJUnit: report Risky test consistently as an error14110ccLeftover from5ce4160a1d0515- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)