Skip to content

chore(deps-dev): bump phpunit/phpunit from 13.4.6 to 13.4.8 - #152

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/composer/develop/phpunit/phpunit-13.4.8
Open

dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/composer/develop/phpunit/phpunit-13.4.8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 22, 2026

Copy link
Copy Markdown
Contributor

Bumps phpunit/phpunit from 13.4.6 to 13.4.8.

Release notes

Sourced from phpunit/phpunit's releases.

PHPUnit 13.4.8

Fixed

  • The baseline generated using --generate-baseline contains an issue once for each time it was triggered, for instance once for each data set of a test that uses a data provider, instead of once
  • A baseline is not applied to the issues that are triggered in a file that is not located in the directory of the baseline, or in a directory below it, for instance when the baseline is located in build/baseline.xml and the file in src
  • When --log-junit php://stdout is used, or php://stdout is configured for the JUnit XML logfile in the XML configuration file, and the test runner prints its regular output, the test runner ends with An error occurred inside PHPUnit after the JUnit XML was printed: the test results are not printed, code coverage reports and the baseline are not written, and the shell exit code is 255
  • When --log-junit php://stdout is used together with --stderr, the JUnit XML is printed to the standard error stream
  • When no test is run, --compact only prints No tests executed! and not why, for instance the PHPUnit error for the invalid data provider of the only test, or the test runner warning for a test class without tests

Learn how to install or update PHPUnit 13.4 in the documentation.

Keep up to date with PHPUnit:

PHPUnit 13.4.7

Fixed

  • When an order is configured on the command line, for instance using --order-by random, defects configured using the executionOrder attribute in the XML configuration file is still applied, and vice versa
  • Using default together with an order for --order-by or the executionOrder XML configuration attribute, for instance default,random, triggers a deprecation for using more than one order, although default resets the order instead of selecting one
  • --fail-on-skipped does not make the test runner exit with a shell exit code that indicates failure when a test class is skipped, for instance because its before-first-test method calls markTestSkipped(), although its tests are counted as skipped
  • --stop-on-skipped does not stop the test run when a test class is skipped, for instance because its before-first-test method calls markTestSkipped()
  • When coverage contribution is required, a test is considered risky because it does not contribute to code coverage although it executed covered code, when the code coverage driver collects hit counts and each covered line that the test executed was executed more than once
  • When PHPUnit is installed using Composer, code units in the PHPUnit\ or SebastianBergmann\ namespace that do not belong to PHPUnit or one of its dependencies are preloaded on startup, which leads to a fatal error when such a code unit depends on code that is not available
  • Code from sebastian/file-filter and sebastian/git-state is not treated like code from PHPUnit's other dependencies, for instance stack frames from it are not filtered from stack traces
  • Code from nikic/php-parser and parts of the code from phar-io/manifest are not treated like code from PHPUnit's other dependencies, for instance stack frames from it are not filtered from stack traces

Learn how to install or update PHPUnit 13.4 in the documentation.

Keep up to date with PHPUnit:

Changelog

Sourced from phpunit/phpunit's changelog.

[13.4.8] - 2026-11-19

Fixed

  • The baseline generated using --generate-baseline contains an issue once for each time it was triggered, for instance once for each data set of a test that uses a data provider, instead of once
  • A baseline is not applied to the issues that are triggered in a file that is not located in the directory of the baseline, or in a directory below it, for instance when the baseline is located in build/baseline.xml and the file in src
  • When --log-junit php://stdout is used, or php://stdout is configured for the JUnit XML logfile in the XML configuration file, and the test runner prints its regular output, the test runner ends with An error occurred inside PHPUnit after the JUnit XML was printed: the test results are not printed, code coverage reports and the baseline are not written, and the shell exit code is 255
  • When --log-junit php://stdout is used together with --stderr, the JUnit XML is printed to the standard error stream
  • When no test is run, --compact only prints No tests executed! and not why, for instance the PHPUnit error for the invalid data provider of the only test, or the test runner warning for a test class without tests

[13.4.7] - 2026-11-13

Fixed

  • When an order is configured on the command line, for instance using --order-by random, defects configured using the executionOrder attribute in the XML configuration file is still applied, and vice versa
  • Using default together with an order for --order-by or the executionOrder XML configuration attribute, for instance default,random, triggers a deprecation for using more than one order, although default resets the order instead of selecting one
  • --fail-on-skipped does not make the test runner exit with a shell exit code that indicates failure when a test class is skipped, for instance because its before-first-test method calls markTestSkipped(), although its tests are counted as skipped
  • --stop-on-skipped does not stop the test run when a test class is skipped, for instance because its before-first-test method calls markTestSkipped()
  • When coverage contribution is required, a test is considered risky because it does not contribute to code coverage although it executed covered code, when the code coverage driver collects hit counts and each covered line that the test executed was executed more than once
  • When PHPUnit is installed using Composer, code units in the PHPUnit\ or SebastianBergmann\ namespace that do not belong to PHPUnit or one of its dependencies are preloaded on startup, which leads to a fatal error when such a code unit depends on code that is not available
  • Code from sebastian/file-filter and sebastian/git-state is not treated like code from PHPUnit's other dependencies, for instance stack frames from it are not filtered from stack traces
  • Code from nikic/php-parser and parts of the code from phar-io/manifest are not treated like code from PHPUnit's other dependencies, for instance stack frames from it are not filtered from stack traces
Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit) from 13.4.6 to 13.4.8.
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.4.8/ChangeLog-13.4.md)
- [Commits](sebastianbergmann/phpunit@13.4.6...13.4.8)

---
updated-dependencies:
- dependency-name: phpunit/phpunit
  dependency-version: 13.4.8
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file php Pull requests that update PHP code labels Nov 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file php Pull requests that update PHP code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants