search

scout-handbook / handbook-api

A back-end API for creating a course handbook connected to SkautIS
MIT License
0 stars 0 forks source link

Bump phpunit/phpunit from 10.5.26 to 11.3.4 #333

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps phpunit/phpunit from 10.5.26 to 11.3.4.

Release notes

Sourced from phpunit/phpunit's releases.

PHPUnit 11.3.4

Fixed

  • #4584: assertJsonStringEqualsJsonString() considers objects with sequential numeric keys equal to be arrays
  • #4625: Generator yielding keys that are neither integer or string leads to hard-to-understand error message when used as data provider
  • #4674: JSON assertions should treat objects as unordered
  • #5891: Callback constraint does not handle variadic arguments correctly when used for mock object expectations
  • #5929: TestDox output containing $ at the beginning gets truncated when used with a data provider
  • #5943: Tests configured to be in group(s) using the XML configuration file are also added to the default group

How to install or update PHPUnit

PHPUnit 11.3.3

Added

  • #5937: failOnPhpunitDeprecation attribute on the <phpunit> element of the XML configuration file and --fail-on-phpunit-deprecation CLI option for controlling whether PHPUnit deprecations should be considered when determining the test runner's shell exit code (default: do not consider)
  • displayDetailsOnPhpunitDeprecations attribute on the <phpunit> element of the XML configuration file and --display-phpunit-deprecations CLI option for controlling whether details on PHPUnit deprecations should be displayed (default: do not display)

Changed

  • #5937: PHPUnit deprecations will, by default, no longer affect the test runner's shell exit code. This can optionally be turned back on using the --fail-on-phpunit-deprecation CLI option or the failOnPhpunitDeprecation="true" attribute on the <phpunit> element of the XML configuration file.
  • Details for PHPUnit deprecations will, by default, no longer be displayed. This can optionally be turned back on using the --display-phpunit-deprecations CLI option or the displayDetailsOnPhpunitDeprecations attribute on the <phpunit> element of the XML configuration file.

How to install or update PHPUnit

PHPUnit 11.3.2

Changed

  • #5931: name property on <testsuites> element in JUnit XML logfile
  • Removed .phpstorm.meta.php file as methods such as TestCase::createStub() use generics / template types for their return types and PhpStorm, for example, uses that information

Fixed

  • #5884: TestDox printer does not consider that issues can be suppressed by attribute, baseline, source location, or @ operator

How to install or update PHPUnit

PHPUnit 11.3.1

Changed

  • Improved how objects are handled for some assertion failure messages

How to install or update PHPUnit

PHPUnit 11.3.0

Added

  • #5869: shortenArraysForExportThreshold attribute on the <phpunit> element of the XML configuration file to limit the export of arrays to a specified number of elements (default: 0 / do not limit the export of arrays)
  • #5885: Optionally repeat TestDox output for non-successful tests after the regular TestDox output
  • #5890: Priority for hook methods

... (truncated)

Changelog

Sourced from phpunit/phpunit's changelog.

[11.3.4] - 2024-09-09

Fixed

  • #4584: assertJsonStringEqualsJsonString() considers objects with sequential numeric keys equal to be arrays
  • #4625: Generator yielding keys that are neither integer or string leads to hard-to-understand error message when used as data provider
  • #4674: JSON assertions should treat objects as unordered
  • #5891: Callback constraint does not handle variadic arguments correctly when used for mock object expectations
  • #5929: TestDox output containing $ at the beginning gets truncated when used with a data provider
  • #5943: Tests configured to be in group(s) using the XML configuration file are also added to the default group

[11.3.3] - 2024-09-04

Added

  • #5937: failOnPhpunitDeprecation attribute on the <phpunit> element of the XML configuration file and --fail-on-phpunit-deprecation CLI option for controlling whether PHPUnit deprecations should be considered when determining the test runner's shell exit code (default: do not consider)
  • displayDetailsOnPhpunitDeprecations attribute on the <phpunit> element of the XML configuration file and --display-phpunit-deprecations CLI option for controlling whether details on PHPUnit deprecations should be displayed (default: do not display)

Changed

  • #5937: PHPUnit deprecations will, by default, no longer affect the test runner's shell exit code. This can optionally be turned back on using the --fail-on-phpunit-deprecation CLI option or the failOnPhpunitDeprecation="true" attribute on the <phpunit> element of the XML configuration file.
  • Details for PHPUnit deprecations will, by default, no longer be displayed. This can optionally be turned back on using the --display-phpunit-deprecations CLI option or the displayDetailsOnPhpunitDeprecations attribute on the <phpunit> element of the XML configuration file.

[11.3.2] - 2024-09-03

Changed

  • #5931: name property on <testsuites> element in JUnit XML logfile
  • Removed .phpstorm.meta.php file as methods such as TestCase::createStub() use generics / template types for their return types and PhpStorm, for example, uses that information

Fixed

  • #5884: TestDox printer does not consider that issues can be suppressed by attribute, baseline, source location, or @ operator

[11.3.1] - 2024-08-13

Changed

  • Improved how objects are handled for some assertion failure messages

[11.3.0] - 2024-08-09

Added

  • #5869: shortenArraysForExportThreshold attribute on the <phpunit> element of the XML configuration file to limit the export of arrays to a specified number of elements (default: 0 / do not limit the export of arrays)
  • #5885: Optionally repeat TestDox output for non-successful tests after the regular TestDox output
  • #5890: Priority for hook methods
  • #5906: --extension CLI option to register a test runner extension

Changed

... (truncated)

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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show 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)
dependabot[bot] commented 2 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.