Skip to content

Bump the all group across 7 directories with 5 updates - #221

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/composer/plugins/cartshift/all-664edebffb
Open

Bump the all group across 7 directories with 5 updates#221
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/composer/plugins/cartshift/all-664edebffb

Conversation

@dependabot

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

Copy link
Copy Markdown

Bumps the all group with 2 updates in the /plugins/cartshift directory: phpunit/phpunit and php-stubs/woocommerce-stubs.
Bumps the all group with 3 updates in the /plugins/fchub-fakturownia directory: phpunit/phpunit, phpstan/phpstan and szepeviktor/phpstan-wordpress.
Bumps the all group with 1 update in the /plugins/fchub-memberships directory: phpunit/phpunit.
Bumps the all group with 3 updates in the /plugins/fchub-multi-currency directory: phpunit/phpunit, phpstan/phpstan and szepeviktor/phpstan-wordpress.
Bumps the all group with 3 updates in the /plugins/fchub-p24 directory: phpunit/phpunit, phpstan/phpstan and szepeviktor/phpstan-wordpress.
Bumps the all group with 3 updates in the /plugins/fchub-thank-you directory: phpunit/phpunit, phpstan/phpstan and squizlabs/php_codesniffer.
Bumps the all group with 3 updates in the /plugins/fchub-wishlist directory: phpunit/phpunit, phpstan/phpstan and szepeviktor/phpstan-wordpress.

Updates phpunit/phpunit from 13.3.1 to 13.4.5

Release notes

Sourced from phpunit/phpunit's releases.

PHPUnit 13.4.5

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

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

Keep up to date with PHPUnit:

PHPUnit 13.4.4

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

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

Keep up to date with PHPUnit:

PHPUnit 13.4.3

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence

... (truncated)

Changelog

Sourced from phpunit/phpunit's changelog.

[13.4.5] - 2026-10-27

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

[13.4.4] - 2026-10-27

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

[13.4.3] - 2026-10-16

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence
  • The Open Test Reporting XML logfile reports an issue that is triggered before a test is prepared, for instance in setUp(), with an empty ID before the start of the test

[13.4.2] - 2026-10-12

Fixed

  • #7033: Compact printer is created although an extension replaces the progress output
  • #7035: Sorting tests by duration recomputes the duration of a test suite for every comparison
  • Sorting tests by size recomputes the size of a test suite for every comparison
  • expectUserDeprecationMessage() and expectUserDeprecationMessageMatches() did not see the deprecations triggered by an attempt of a retried test and saw those of the previously run test instead
  • The status of a test whose mock object raises an exception in its destructor is success although the test is reported as errored, so #[Retry] does not retry the test, --repeat does not skip the remaining repetitions, tearDown() sees the wrong status, and code coverage records the test as successful
  • Named arguments passed to with() were matched by position instead of by name, so an expectation such as ->with(b: 7) compared the expected value with the first parameter of the method and the parameter named $b was not checked
  • String keys of the parameter sets passed to withParameterSetsInOrder(), withParameterSetsInAnyOrder(), and withParameterSetsInPartialOrder() were ignored, so a parameter set such as ['b' => 7] compared the expected value with the first parameter of the method and the parameter named $b was not checked

... (truncated)

Commits
  • 941457a Prepare release
  • 2080b37 Merge branch '12.5' into 13.4
  • 1d6dbe7 Prepare release
  • ef98204 Merge branch '12.5' into 13.4
  • 15fb431 Do not require the POSIX extension for using the automatically created static...
  • 71b681a Prepare release
  • c056074 Merge branch '12.5' into 13.4
  • 191b2e0 Prepare release
  • ae31c78 Create the temporary files for collecting code coverage for a PHPT test in a ...
  • c4c4f06 Merge branch '12.5' into 13.4
  • Additional commits viewable in compare view

Updates php-stubs/woocommerce-stubs from 9.9.5 to 11.2.0

Commits
  • fb590c1 Generate stubs for WooCommerce 11.2.0
  • 06dfedf Generate stubs for WooCommerce 11.1.2
  • b34e5fa Generate stubs for WooCommerce 11.1.1
  • aea38d3 Replace my FU-style message
  • 179fee6 Generate stubs for WooCommerce 11.1.0
  • 89729df Generate stubs for WooCommerce 11.0.1
  • 923dd29 Generate stubs for WooCommerce 11.0.0
  • ea9b2a6 Fix overly broad Api path exclusion (#33)
  • a569e43 Generate stubs for WooCommerce 10.9.4
  • 0c37ae3 Bump the WP stubs requirement (#32)
  • Additional commits viewable in compare view

Updates phpunit/phpunit from 13.3.1 to 13.4.5

Release notes

Sourced from phpunit/phpunit's releases.

PHPUnit 13.4.5

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

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

Keep up to date with PHPUnit:

PHPUnit 13.4.4

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

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

Keep up to date with PHPUnit:

PHPUnit 13.4.3

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence

... (truncated)

Changelog

Sourced from phpunit/phpunit's changelog.

[13.4.5] - 2026-10-27

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

[13.4.4] - 2026-10-27

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

[13.4.3] - 2026-10-16

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence
  • The Open Test Reporting XML logfile reports an issue that is triggered before a test is prepared, for instance in setUp(), with an empty ID before the start of the test

[13.4.2] - 2026-10-12

Fixed

  • #7033: Compact printer is created although an extension replaces the progress output
  • #7035: Sorting tests by duration recomputes the duration of a test suite for every comparison
  • Sorting tests by size recomputes the size of a test suite for every comparison
  • expectUserDeprecationMessage() and expectUserDeprecationMessageMatches() did not see the deprecations triggered by an attempt of a retried test and saw those of the previously run test instead
  • The status of a test whose mock object raises an exception in its destructor is success although the test is reported as errored, so #[Retry] does not retry the test, --repeat does not skip the remaining repetitions, tearDown() sees the wrong status, and code coverage records the test as successful
  • Named arguments passed to with() were matched by position instead of by name, so an expectation such as ->with(b: 7) compared the expected value with the first parameter of the method and the parameter named $b was not checked
  • String keys of the parameter sets passed to withParameterSetsInOrder(), withParameterSetsInAnyOrder(), and withParameterSetsInPartialOrder() were ignored, so a parameter set such as ['b' => 7] compared the expected value with the first parameter of the method and the parameter named $b was not checked

... (truncated)

Commits
  • 941457a Prepare release
  • 2080b37 Merge branch '12.5' into 13.4
  • 1d6dbe7 Prepare release
  • ef98204 Merge branch '12.5' into 13.4
  • 15fb431 Do not require the POSIX extension for using the automatically created static...
  • 71b681a Prepare release
  • c056074 Merge branch '12.5' into 13.4
  • 191b2e0 Prepare release
  • ae31c78 Create the temporary files for collecting code coverage for a PHPT test in a ...
  • c4c4f06 Merge branch '12.5' into 13.4
  • Additional commits viewable in compare view

Updates phpstan/phpstan from 2.2.8 to 2.3.4

Commits

Updates szepeviktor/phpstan-wordpress from 2.0.3 to 2.0.4

Release notes

Sourced from szepeviktor/phpstan-wordpress's releases.

Support WP 7

What's Changed

Full Changelog: szepeviktor/phpstan-wordpress@v2.0.3...v2.0.4

Commits
  • 84577e2 Adjust the wordpress-stubs dependency version range so version 7.0 can be use...
  • See full diff in compare view

Updates phpunit/phpunit from 13.3.1 to 13.4.5

Release notes

Sourced from phpunit/phpunit's releases.

PHPUnit 13.4.5

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

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

Keep up to date with PHPUnit:

PHPUnit 13.4.4

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

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

Keep up to date with PHPUnit:

PHPUnit 13.4.3

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence

... (truncated)

Changelog

Sourced from phpunit/phpunit's changelog.

[13.4.5] - 2026-10-27

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

[13.4.4] - 2026-10-27

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

[13.4.3] - 2026-10-16

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence
  • The Open Test Reporting XML logfile reports an issue that is triggered before a test is prepared, for instance in setUp(), with an empty ID before the start of the test

[13.4.2] - 2026-10-12

Fixed

  • #7033: Compact printer is created although an extension replaces the progress output
  • #7035: Sorting tests by duration recomputes the duration of a test suite for every comparison
  • Sorting tests by size recomputes the size of a test suite for every comparison
  • expectUserDeprecationMessage() and expectUserDeprecationMessageMatches() did not see the deprecations triggered by an attempt of a retried test and saw those of the previously run test instead
  • The status of a test whose mock object raises an exception in its destructor is success although the test is reported as errored, so #[Retry] does not retry the test, --repeat does not skip the remaining repetitions, tearDown() sees the wrong status, and code coverage records the test as successful
  • Named arguments passed to with() were matched by position instead of by name, so an expectation such as ->with(b: 7) compared the expected value with the first parameter of the method and the parameter named $b was not checked
  • String keys of the parameter sets passed to withParameterSetsInOrder(), withParameterSetsInAnyOrder(), and withParameterSetsInPartialOrder() were ignored, so a parameter set such as ['b' => 7] compared the expected value with the first parameter of the method and the parameter named $b was not checked

... (truncated)

Commits
  • 941457a Prepare release
  • 2080b37 Merge branch '12.5' into 13.4
  • 1d6dbe7 Prepare release
  • ef98204 Merge branch '12.5' into 13.4
  • 15fb431 Do not require the POSIX extension for using the automatically created static...
  • 71b681a Prepare release
  • c056074 Merge branch '12.5' into 13.4
  • 191b2e0 Prepare release
  • ae31c78 Create the temporary files for collecting code coverage for a PHPT test in a ...
  • c4c4f06 Merge branch '12.5' into 13.4
  • Additional commits viewable in compare view

Updates phpunit/phpunit from 13.3.1 to 13.4.5

Release notes

Sourced from phpunit/phpunit's releases.

PHPUnit 13.4.5

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

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

Keep up to date with PHPUnit:

PHPUnit 13.4.4

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

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

Keep up to date with PHPUnit:

PHPUnit 13.4.3

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence

... (truncated)

Changelog

Sourced from phpunit/phpunit's changelog.

[13.4.5] - 2026-10-27

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

[13.4.4] - 2026-10-27

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

[13.4.3] - 2026-10-16

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence
  • The Open Test Reporting XML logfile reports an issue that is triggered before a test is prepared, for instance in setUp(), with an empty ID before the start of the test

[13.4.2] - 2026-10-12

Fixed

  • #7033: Compact printer is created although an extension replaces the progress output
  • #7035: Sorting tests by duration recomputes the duration of a test suite for every comparison
  • Sorting tests by size recomputes the size of a test suite for every comparison
  • expectUserDeprecationMessage() and expectUserDeprecationMessageMatches() did not see the deprecations triggered by an attempt of a retried test and saw those of the previously run test instead
  • The status of a test whose mock object raises an exception in its destructor is success although the test is reported as errored, so #[Retry] does not retry the test, --repeat does not skip the remaining repetitions, tearDown() sees the wrong status, and code coverage records the test as successful
  • Named arguments passed to with() were matched by position instead of by name, so an expectation such as ->with(b: 7) compared the expected value with the first parameter of the method and the parameter named $b was not checked
  • String keys of the parameter sets passed to withParameterSetsInOrder(), withParameterSetsInAnyOrder(), and withParameterSetsInPartialOrder() were ignored, so a parameter set such as ['b' => 7] compared the expected value with the first parameter of the method and the parameter named $b was not checked

... (truncated)

Commits
  • 941457a Prepare release
  • 2080b37 Merge branch '12.5' into 13.4
  • 1d6dbe7 Prepare release
  • ef98204 Merge branch '12.5' into 13.4
  • 15fb431 Do not require the POSIX extension for using the automatically created static...
  • 71b681a Prepare release
  • c056074 Merge branch '12.5' into 13.4
  • 191b2e0 Prepare release
  • ae31c78 Create the temporary files for collecting code coverage for a PHPT test in a ...
  • c4c4f06 Merge branch '12.5' into 13.4
  • Additional commits viewable in compare view

Updates phpstan/phpstan from 2.2.8 to 2.3.4

Commits

Updates szepeviktor/phpstan-wordpress from 2.0.3 to 2.0.4

Release notes

Sourced from szepeviktor/phpstan-wordpress's releases.

Support WP 7

What's Changed

Full Changelog: https://...

Description has been truncated

@dependabot
Bump the all group across 7 directories with 5 updates
4c1f8cf 
Bumps the all group with 2 updates in the /plugins/cartshift directory: [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit) and [php-stubs/woocommerce-stubs](https://github.com/php-stubs/woocommerce-stubs).
Bumps the all group with 3 updates in the /plugins/fchub-fakturownia directory: [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit), [phpstan/phpstan](https://github.com/phpstan/phpstan-phar-composer-source) and [szepeviktor/phpstan-wordpress](https://github.com/szepeviktor/phpstan-wordpress).
Bumps the all group with 1 update in the /plugins/fchub-memberships directory: [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit).
Bumps the all group with 3 updates in the /plugins/fchub-multi-currency directory: [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit), [phpstan/phpstan](https://github.com/phpstan/phpstan-phar-composer-source) and [szepeviktor/phpstan-wordpress](https://github.com/szepeviktor/phpstan-wordpress).
Bumps the all group with 3 updates in the /plugins/fchub-p24 directory: [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit), [phpstan/phpstan](https://github.com/phpstan/phpstan-phar-composer-source) and [szepeviktor/phpstan-wordpress](https://github.com/szepeviktor/phpstan-wordpress).
Bumps the all group with 3 updates in the /plugins/fchub-thank-you directory: [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit), [phpstan/phpstan](https://github.com/phpstan/phpstan-phar-composer-source) and [squizlabs/php_codesniffer](https://github.com/PHPCSStandards/PHP_CodeSniffer).
Bumps the all group with 3 updates in the /plugins/fchub-wishlist directory: [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit), [phpstan/phpstan](https://github.com/phpstan/phpstan-phar-composer-source) and [szepeviktor/phpstan-wordpress](https://github.com/szepeviktor/phpstan-wordpress).


Updates `phpunit/phpunit` from 13.3.1 to 13.4.5
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.4.5/ChangeLog-13.4.md)
- [Commits](sebastianbergmann/phpunit@13.3.1...13.4.5)

Updates `php-stubs/woocommerce-stubs` from 9.9.5 to 11.2.0
- [Commits](php-stubs/woocommerce-stubs@v9.9.5...v11.2.0)

Updates `phpunit/phpunit` from 13.3.1 to 13.4.5
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.4.5/ChangeLog-13.4.md)
- [Commits](sebastianbergmann/phpunit@13.3.1...13.4.5)

Updates `phpstan/phpstan` from 2.2.8 to 2.3.4
- [Commits](https://github.com/phpstan/phpstan-phar-composer-source/commits)

Updates `szepeviktor/phpstan-wordpress` from 2.0.3 to 2.0.4
- [Release notes](https://github.com/szepeviktor/phpstan-wordpress/releases)
- [Commits](szepeviktor/phpstan-wordpress@v2.0.3...v2.0.4)

Updates `phpunit/phpunit` from 13.3.1 to 13.4.5
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.4.5/ChangeLog-13.4.md)
- [Commits](sebastianbergmann/phpunit@13.3.1...13.4.5)

Updates `phpunit/phpunit` from 13.3.1 to 13.4.5
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.4.5/ChangeLog-13.4.md)
- [Commits](sebastianbergmann/phpunit@13.3.1...13.4.5)

Updates `phpstan/phpstan` from 2.2.8 to 2.3.4
- [Commits](https://github.com/phpstan/phpstan-phar-composer-source/commits)

Updates `szepeviktor/phpstan-wordpress` from 2.0.3 to 2.0.4
- [Release notes](https://github.com/szepeviktor/phpstan-wordpress/releases)
- [Commits](szepeviktor/phpstan-wordpress@v2.0.3...v2.0.4)

Updates `phpunit/phpunit` from 13.3.1 to 13.4.5
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.4.5/ChangeLog-13.4.md)
- [Commits](sebastianbergmann/phpunit@13.3.1...13.4.5)

Updates `phpstan/phpstan` from 2.2.8 to 2.3.4
- [Commits](https://github.com/phpstan/phpstan-phar-composer-source/commits)

Updates `szepeviktor/phpstan-wordpress` from 2.0.3 to 2.0.4
- [Release notes](https://github.com/szepeviktor/phpstan-wordpress/releases)
- [Commits](szepeviktor/phpstan-wordpress@v2.0.3...v2.0.4)

Updates `phpunit/phpunit` from 13.3.1 to 13.4.5
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.4.5/ChangeLog-13.4.md)
- [Commits](sebastianbergmann/phpunit@13.3.1...13.4.5)

Updates `phpstan/phpstan` from 2.2.8 to 2.3.4
- [Commits](https://github.com/phpstan/phpstan-phar-composer-source/commits)

Updates `squizlabs/php_codesniffer` from 3.13.6 to 4.0.4
- [Release notes](https://github.com/PHPCSStandards/PHP_CodeSniffer/releases)
- [Changelog](https://github.com/PHPCSStandards/PHP_CodeSniffer/blob/4.x/CHANGELOG-3.x.md)
- [Commits](PHPCSStandards/PHP_CodeSniffer@3.13.6...4.0.4)

Updates `phpunit/phpunit` from 13.3.1 to 13.4.5
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.4.5/ChangeLog-13.4.md)
- [Commits](sebastianbergmann/phpunit@13.3.1...13.4.5)

Updates `phpstan/phpstan` from 2.2.8 to 2.3.4
- [Commits](https://github.com/phpstan/phpstan-phar-composer-source/commits)

Updates `szepeviktor/phpstan-wordpress` from 2.0.3 to 2.0.4
- [Release notes](https://github.com/szepeviktor/phpstan-wordpress/releases)
- [Commits](szepeviktor/phpstan-wordpress@v2.0.3...v2.0.4)

---
updated-dependencies:
- dependency-name: phpunit/phpunit
  dependency-version: 13.4.5
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: php-stubs/woocommerce-stubs
  dependency-version: 11.2.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: all
- dependency-name: phpunit/phpunit
  dependency-version: 13.4.5
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: phpstan/phpstan
  dependency-version: 2.3.4
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: szepeviktor/phpstan-wordpress
  dependency-version: 2.0.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: phpunit/phpunit
  dependency-version: 13.4.5
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: phpunit/phpunit
  dependency-version: 13.4.5
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: phpstan/phpstan
  dependency-version: 2.3.4
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: szepeviktor/phpstan-wordpress
  dependency-version: 2.0.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: phpunit/phpunit
  dependency-version: 13.4.5
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: phpstan/phpstan
  dependency-version: 2.3.4
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: szepeviktor/phpstan-wordpress
  dependency-version: 2.0.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: phpunit/phpunit
  dependency-version: 13.4.5
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: phpstan/phpstan
  dependency-version: 2.3.4
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: squizlabs/php_codesniffer
  dependency-version: 4.0.4
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: all
- dependency-name: phpunit/phpunit
  dependency-version: 13.4.5
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: phpstan/phpstan
  dependency-version: 2.3.4
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: szepeviktor/phpstan-wordpress
  dependency-version: 2.0.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
...

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 1, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 1, 2026 •
edited
Loading

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-01T05:13:24.145044Z 4c1f8cf PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

This branch has not been deployed

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

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants