Skip to content

chore(deps): Update dependency phpunit/phpunit to v13.4.8 - #370

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/phpunit-phpunit-13.x-lockfile
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/phpunit-phpunit-13.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
phpunit/phpunit (source) 13.4.5 → 13.4.8 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

sebastianbergmann/phpunit (phpunit/phpunit)

v13.4.8: PHPUnit 13.4.8

Compare Source

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:

v13.4.7: PHPUnit 13.4.7

Compare Source

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:

v13.4.6: PHPUnit 13.4.6

Compare Source

Changed
  • Issues whose message refers to an anonymous class could not be ignored using a baseline on PHP 8.6 (as of PHP 8.6, such messages contain the full name of the anonymous class: a NUL byte followed by the file, line, and a counter)
  • Make PHAR build reproducible across filesystems (files are now added to the PHAR sorted by their path instead of in the order in which the filesystem lists them)
Fixed
  • When method() is called for a method of a test double that cannot be configured, for instance because it does not exist, every subsequent invocation of a method of that test double fails with Method name is not configured
  • When a hook method of a test, for instance setUp(), marks the test as incomplete, the hook method is reported as failed
  • When an "after test" method, for instance tearDown(), marks a successful test as incomplete or skips it, the test is reported as failed
  • When a before-first-test method, for instance setUpBeforeClass(), calls markTestIncomplete(), each test of the test class is reported as failed instead of the test class being skipped as it is when markTestSkipped() is called
  • When an after-last-test method, for instance tearDownAfterClass(), calls markTestIncomplete() or markTestSkipped() after the tests of the test class have been run, this is reported as a failure, also for each test of the test class that is run in process isolation
  • A failed PHP assertion, made using assert(), in a hook method is reported as an error of that method instead of as a failure, and it is counted as an error instead of as a failure when that method is a before-first-test method or an after-last-test method
  • When an assertion fails in an "after test" method, for instance tearDown(), of a test that already failed, errored, or was marked as incomplete, a failure is reported in addition to the outcome of the test, so the test is counted more than once and onNotSuccessfulTest() is called with the failure from the "after test" method instead of the test's own
  • When a test fails because of an exception of a registered failure type, an error or a failure in an "after test" method, for instance tearDown(), is reported in addition to the test's failure, so the test is counted more than once
  • A test that fails because of an exception of a registered failure type is considered risky when it does not perform assertions or, when requireCoverageMetadata="true" is configured, when it does not define a code coverage target, unlike a test that fails because an assertion failed
  • The TestDox output does not show the failure of a before-first-test method or an after-last-test method, for instance an assertion failure in setUpBeforeClass()
  • Control characters and ANSI escape sequences in user-supplied strings are not made visible in the output of --debug and in the logfiles written by --log-events-text and --log-events-verbose-text
  • Groups configured for a test directory or test file using the groups attribute of <directory> or <file> in the XML configuration file are not assigned to PHPT tests, so --group and --exclude-group do not select them and --list-groups and --list-tests-xml report them as being in the default group or not at all
Removed
  • The library PHAR (phpunit-library-X.Y.Z.phar) is no longer built, it could not be loaded since PHPUnit 9.5.8

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

Keep up to date with PHPUnit:

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependency An issue or pull request targeting dependencies. label Nov 2, 2026
@renovate
renovate Bot force-pushed the renovate/phpunit-phpunit-13.x-lockfile branch from ae5e971 to 87d40bc Compare November 13, 2026 17:06
@renovate renovate Bot changed the title chore(deps): Update dependency phpunit/phpunit to v13.4.6 chore(deps): Update dependency phpunit/phpunit to v13.4.7 Nov 13, 2026
@renovate renovate Bot changed the title chore(deps): Update dependency phpunit/phpunit to v13.4.7 chore(deps): Update dependency phpunit/phpunit to v13.4.8 Nov 19, 2026
@renovate

renovate Bot commented Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - vimeo/psalm is locked to version 6.20.3 and an update of this package was not requested.
    - vimeo/psalm 6.20.3 requires php ~8.1.31 || ~8.2.27 || ~8.3.16 || ~8.4.3 || ~8.5.0 -> your php version (8.6.0) does not satisfy that requirement.
  Problem 2
    - psalm/plugin-phpunit is locked to version 0.19.7 and an update of this package was not requested.
    - psalm/plugin-phpunit 0.19.7 requires vimeo/psalm dev-master || ^6.10.0 -> satisfiable by vimeo/psalm[6.20.3].
    - vimeo/psalm 6.20.3 requires php ~8.1.31 || ~8.2.27 || ~8.3.16 || ~8.4.3 || ~8.5.0 -> your php version (8.6.0) does not satisfy that requirement.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependency An issue or pull request targeting dependencies.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants