[web-php] PR #1065: composer(deps-dev): bump phpunit/phpunit from 11.3.1 to 11.3.4
| From: | dependabot[bot] | Date: | Mon, 09 Sep 2024 16:04:59 +0000 |
| Subject: | [web-php] PR #1065: composer(deps-dev): bump phpunit/phpunit from 11.3.1 to 11.3.4 | ||
| Groups: | php.webmaster | ||
| Request: | Send a blank email to php-webmaster+get-32068@lists.php.net to get a copy of this message | ||
Pull Request: https://github.com/php/web-php/pull/1065
Author: dependabot[bot]
Bumps [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit) from 11.3.1 to 11.3.4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/sebastianbergmann/phpunit/releases">phpunit/phpunit's
releases</a>.</em></p>
<blockquote>
<h2>PHPUnit 11.3.4</h2>
<h3>Fixed</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/4584">#4584</a>:
<code>assertJsonStringEqualsJsonString()</code> considers objects with sequential
numeric keys equal to be arrays</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/4625">#4625</a>:
Generator yielding keys that are neither integer or string leads to hard-to-understand error message
when used as data provider</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/4674">#4674</a>:
JSON assertions should treat objects as unordered</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5891">#5891</a>:
<code>Callback</code> constraint does not handle variadic arguments correctly when used
for mock object expectations</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5929">#5929</a>:
TestDox output containing <code>$</code> at the beginning gets truncated when used with
a data provider</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5943">#5943</a>:
Tests configured to be in group(s) using the XML configuration file are also added to the
<code>default</code> group</li>
</ul>
<hr />
<p><a href="https://docs.phpunit.de/en/11.3/installation.html">How
to install or update PHPUnit</a></p>
<h2>PHPUnit 11.3.3</h2>
<h3>Added</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5937">#5937</a>:
<code>failOnPhpunitDeprecation</code> attribute on the
<code><phpunit></code> element of the XML configuration file and
<code>--fail-on-phpunit-deprecation</code> CLI option for controlling whether PHPUnit
deprecations should be considered when determining the test runner's shell exit code (default:
do not consider)</li>
<li><code>displayDetailsOnPhpunitDeprecations</code> attribute on the
<code><phpunit></code> element of the XML configuration file and
<code>--display-phpunit-deprecations</code> CLI option for controlling whether details
on PHPUnit deprecations should be displayed (default: do not display)</li>
</ul>
<h3>Changed</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5937">#5937</a>:
PHPUnit deprecations will, by default, no longer affect the test runner's shell exit code. This
can optionally be turned back on using the <code>--fail-on-phpunit-deprecation</code>
CLI option or the <code>failOnPhpunitDeprecation="true"</code>
attribute on the <code><phpunit></code> element of the XML configuration
file.</li>
<li>Details for PHPUnit deprecations will, by default, no longer be displayed. This can
optionally be turned back on using the <code>--display-phpunit-deprecations</code> CLI
option or the <code>displayDetailsOnPhpunitDeprecations</code> attribute on the
<code><phpunit></code> element of the XML configuration file.</li>
</ul>
<hr />
<p><a href="https://docs.phpunit.de/en/11.3/installation.html">How
to install or update PHPUnit</a></p>
<h2>PHPUnit 11.3.2</h2>
<h3>Changed</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/pull/5931">#5931</a>:
<code>name</code> property on <code><testsuites></code>
element in JUnit XML logfile</li>
<li>Removed <code>.phpstorm.meta.php</code> file as methods such as
<code>TestCase::createStub()</code> use generics / template types for their return types
and PhpStorm, for example, uses that information</li>
</ul>
<h3>Fixed</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5884">#5884</a>:
TestDox printer does not consider that issues can be suppressed by attribute, baseline, source
location, or <code>@</code> operator</li>
</ul>
<hr />
<p><a href="https://docs.phpunit.de/en/11.3/installation.html">How
to install or update PHPUnit</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/sebastianbergmann/phpunit/blob/11.3.4/ChangeLog-11.3.md">phpunit/phpunit's
changelog</a>.</em></p>
<blockquote>
<h2>[11.3.4] - 2024-09-09</h2>
<h3>Fixed</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/4584">#4584</a>:
<code>assertJsonStringEqualsJsonString()</code> considers objects with sequential
numeric keys equal to be arrays</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/4625">#4625</a>:
Generator yielding keys that are neither integer or string leads to hard-to-understand error message
when used as data provider</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/4674">#4674</a>:
JSON assertions should treat objects as unordered</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5891">#5891</a>:
<code>Callback</code> constraint does not handle variadic arguments correctly when used
for mock object expectations</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5929">#5929</a>:
TestDox output containing <code>$</code> at the beginning gets truncated when used with
a data provider</li>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5943">#5943</a>:
Tests configured to be in group(s) using the XML configuration file are also added to the
<code>default</code> group</li>
</ul>
<h2>[11.3.3] - 2024-09-04</h2>
<h3>Added</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5937">#5937</a>:
<code>failOnPhpunitDeprecation</code> attribute on the
<code><phpunit></code> element of the XML configuration file and
<code>--fail-on-phpunit-deprecation</code> CLI option for controlling whether PHPUnit
deprecations should be considered when determining the test runner's shell exit code (default:
do not consider)</li>
<li><code>displayDetailsOnPhpunitDeprecations</code> attribute on the
<code><phpunit></code> element of the XML configuration file and
<code>--display-phpunit-deprecations</code> CLI option for controlling whether details
on PHPUnit deprecations should be displayed (default: do not display)</li>
</ul>
<h3>Changed</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5937">#5937</a>:
PHPUnit deprecations will, by default, no longer affect the test runner's shell exit code. This
can optionally be turned back on using the <code>--fail-on-phpunit-deprecation</code>
CLI option or the <code>failOnPhpunitDeprecation="true"</code>
attribute on the <code><phpunit></code> element of the XML configuration
file.</li>
<li>Details for PHPUnit deprecations will, by default, no longer be displayed. This can
optionally be turned back on using the <code>--display-phpunit-deprecations</code> CLI
option or the <code>displayDetailsOnPhpunitDeprecations</code> attribute on the
<code><phpunit></code> element of the XML configuration file.</li>
</ul>
<h2>[11.3.2] - 2024-09-03</h2>
<h3>Changed</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/pull/5931">#5931</a>:
<code>name</code> property on <code><testsuites></code>
element in JUnit XML logfile</li>
<li>Removed <code>.phpstorm.meta.php</code> file as methods such as
<code>TestCase::createStub()</code> use generics / template types for their return types
and PhpStorm, for example, uses that information</li>
</ul>
<h3>Fixed</h3>
<ul>
<li><a href="https://redirect.github.com/sebastianbergmann/phpunit/issues/5884">#5884</a>:
TestDox printer does not consider that issues can be suppressed by attribute, baseline, source
location, or <code>@</code> operator</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/d2ef57db1410b102b250e0cdce6675a60c2a993d"><code>d2ef57d</code></a>
Prepare release</li>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/a3c2ef362b2155e051241c0fa2adc25adec0886d"><code>a3c2ef3</code></a>
Merge branch '10.5' into 11.3</li>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/4def7a9cda75af9c2bc179ed53a8e41313e7f7cf"><code>4def7a9</code></a>
Prepare release</li>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/7ab77541911050da9cb08a1d386c55829fd8c2f4"><code>7ab7754</code></a>
Fix</li>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/48b15e2a1d623983c77aa8edbb9db40eb1d640da"><code>48b15e2</code></a>
Merge branch '10.5' into 11.3</li>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/441ccc756a79aba7c2fc1b9e471044dc74a9a3d9"><code>441ccc7</code></a>
Update ChangeLog</li>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/ab2cd21adca01223e5b762cf1acc72a9500977f5"><code>ab2cd21</code></a>
Change PHP_INT_MAX to null and update end-to-end tests</li>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/c2dc716dbcf4b55f32077e42b4d780edac8d0a83"><code>c2dc716</code></a>
Do not use the ternary operator</li>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/1c004af0baaa0adb6456f2a758e380dc1d87f204"><code>1c004af</code></a>
Renaming</li>
<li><a href="https://github.com/sebastianbergmann/phpunit/commit/18911e55e9a18d473668406a246346bed4a8afdc"><code>18911e5</code></a>
Fix variadic function as callback</li>
<li>Additional commits viewable in <a href="https://github.com/sebastianbergmann/phpunit/compare/11.3.1...11.3.4">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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 <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)
</details>