dependabot[bot] opened a new pull request, #2142: URL: https://github.com/apache/apisix-ingress-controller/pull/2142
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.13.2 to 2.15.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/onsi/ginkgo/releases">github.com/onsi/ginkgo/v2's releases</a>.</em></p> <blockquote> <h2>v2.15.0</h2> <h2>2.15.0</h2> <h3>Features</h3> <ul> <li>JUnit reports now interpret Label(owner:X) and set owner to X. [8f3bd70]</li> <li>include cancellation reason when cancelling spec context [96e915c]</li> </ul> <h3>Fixes</h3> <ul> <li>emit output of failed go tool cover invocation so users can try to debug things for themselves [c245d09]</li> <li>fix outline when using nodot in ginkgo v2 [dca77c8]</li> <li>Document areas where GinkgoT() behaves differently from testing.T [dbaf18f]</li> <li>bugfix(docs): use Unsetenv instead of Clearenv (<a href="https://redirect.github.com/onsi/ginkgo/issues/1337">#1337</a>) [6f67a14]</li> </ul> <h3>Maintenance</h3> <ul> <li>Bump to go 1.20 [4fcd0b3]</li> </ul> <h2>v2.14.0</h2> <h2>2.14.0</h2> <h3>Features</h3> <p>You can now use <code>GinkgoTB()</code> when you need an instance of <code>testing.TB</code> to pass to a library.</p> <p>Prior to this release table testing only supported generating individual <code>It</code>s for each test entry. <code>DescribeTableSubtree</code> extends table testing support to entire testing subtrees - under the hood <code>DescrieTableSubtree</code> generates a new container for each entry and invokes your function to fill our the container. See the <a href="https://onsi.github.io/ginkgo/#generating-subtree-tables">docs</a> to learn more.</p> <ul> <li>Introduce DescribeTableSubtree [65ec56d]</li> <li>add GinkgoTB() to docs [4a2c832]</li> <li>Add GinkgoTB() function (<a href="https://redirect.github.com/onsi/ginkgo/issues/1333">#1333</a>) [92b6744]</li> </ul> <h3>Fixes</h3> <ul> <li>Fix typo in internal/suite.go (<a href="https://redirect.github.com/onsi/ginkgo/issues/1332">#1332</a>) [beb9507]</li> <li>Fix typo in docs/index.md (<a href="https://redirect.github.com/onsi/ginkgo/issues/1319">#1319</a>) [4ac3a13]</li> <li>allow wasm to compile with ginkgo present (<a href="https://redirect.github.com/onsi/ginkgo/issues/1311">#1311</a>) [b2e5bc5]</li> </ul> <h3>Maintenance</h3> <ul> <li>Bump golang.org/x/tools from 0.16.0 to 0.16.1 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1316">#1316</a>) [465a8ec]</li> <li>Bump actions/setup-go from 4 to 5 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1313">#1313</a>) [eab0e40]</li> <li>Bump github/codeql-action from 2 to 3 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1317">#1317</a>) [fbf9724]</li> <li>Bump golang.org/x/crypto (<a href="https://redirect.github.com/onsi/ginkgo/issues/1318">#1318</a>) [3ee80ee]</li> <li>Bump golang.org/x/tools from 0.14.0 to 0.16.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1306">#1306</a>) [123e1d5]</li> <li>Bump github.com/onsi/gomega from 1.29.0 to 1.30.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1297">#1297</a>) [558f6e0]</li> <li>Bump golang.org/x/net from 0.17.0 to 0.19.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1307">#1307</a>) [84ff7f3]</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/onsi/ginkgo/blob/master/CHANGELOG.md">github.com/onsi/ginkgo/v2's changelog</a>.</em></p> <blockquote> <h2>2.15.0</h2> <h3>Features</h3> <ul> <li>JUnit reports now interpret Label(owner:X) and set owner to X. [8f3bd70]</li> <li>include cancellation reason when cancelling spec context [96e915c]</li> </ul> <h3>Fixes</h3> <ul> <li>emit output of failed go tool cover invocation so users can try to debug things for themselves [c245d09]</li> <li>fix outline when using nodot in ginkgo v2 [dca77c8]</li> <li>Document areas where GinkgoT() behaves differently from testing.T [dbaf18f]</li> <li>bugfix(docs): use Unsetenv instead of Clearenv (<a href="https://redirect.github.com/onsi/ginkgo/issues/1337">#1337</a>) [6f67a14]</li> </ul> <h3>Maintenance</h3> <ul> <li>Bump to go 1.20 [4fcd0b3]</li> </ul> <h2>2.14.0</h2> <h3>Features</h3> <p>You can now use <code>GinkgoTB()</code> when you need an instance of <code>testing.TB</code> to pass to a library.</p> <p>Prior to this release table testing only supported generating individual <code>It</code>s for each test entry. <code>DescribeTableSubtree</code> extends table testing support to entire testing subtrees - under the hood <code>DescrieTableSubtree</code> generates a new container for each entry and invokes your function to fill our the container. See the <a href="https://onsi.github.io/ginkgo/#generating-subtree-tables">docs</a> to learn more.</p> <ul> <li>Introduce DescribeTableSubtree [65ec56d]</li> <li>add GinkgoTB() to docs [4a2c832]</li> <li>Add GinkgoTB() function (<a href="https://redirect.github.com/onsi/ginkgo/issues/1333">#1333</a>) [92b6744]</li> </ul> <h3>Fixes</h3> <ul> <li>Fix typo in internal/suite.go (<a href="https://redirect.github.com/onsi/ginkgo/issues/1332">#1332</a>) [beb9507]</li> <li>Fix typo in docs/index.md (<a href="https://redirect.github.com/onsi/ginkgo/issues/1319">#1319</a>) [4ac3a13]</li> <li>allow wasm to compile with ginkgo present (<a href="https://redirect.github.com/onsi/ginkgo/issues/1311">#1311</a>) [b2e5bc5]</li> </ul> <h3>Maintenance</h3> <ul> <li>Bump golang.org/x/tools from 0.16.0 to 0.16.1 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1316">#1316</a>) [465a8ec]</li> <li>Bump actions/setup-go from 4 to 5 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1313">#1313</a>) [eab0e40]</li> <li>Bump github/codeql-action from 2 to 3 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1317">#1317</a>) [fbf9724]</li> <li>Bump golang.org/x/crypto (<a href="https://redirect.github.com/onsi/ginkgo/issues/1318">#1318</a>) [3ee80ee]</li> <li>Bump golang.org/x/tools from 0.14.0 to 0.16.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1306">#1306</a>) [123e1d5]</li> <li>Bump github.com/onsi/gomega from 1.29.0 to 1.30.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1297">#1297</a>) [558f6e0]</li> <li>Bump golang.org/x/net from 0.17.0 to 0.19.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1307">#1307</a>) [84ff7f3]</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/onsi/ginkgo/commit/7fa019079a7b6cfe92acac92df4a84f2748e45a4"><code>7fa0190</code></a> v2.15.0</li> <li><a href="https://github.com/onsi/ginkgo/commit/c245d09a1a083f643ad2b91878cf060146cc94e3"><code>c245d09</code></a> emit output of failed go tool cover invocation so users can try to debug thin...</li> <li><a href="https://github.com/onsi/ginkgo/commit/dca77c807c02fbc18dcc957c8e605424dbb5a891"><code>dca77c8</code></a> fix outline when using nodot inginkgo v2</li> <li><a href="https://github.com/onsi/ginkgo/commit/96e915c326d0265f3bb0f662672573f124fcd38d"><code>96e915c</code></a> include cancellation reason when cancelling spec context</li> <li><a href="https://github.com/onsi/ginkgo/commit/4fcd0b3559d887317826a9d604b947d6b2b52b1c"><code>4fcd0b3</code></a> Bump to go 1.20</li> <li><a href="https://github.com/onsi/ginkgo/commit/732abbc3e709c4913e7f0644c1aee1faf076f0ea"><code>732abbc</code></a> clarify that last owner label wins</li> <li><a href="https://github.com/onsi/ginkgo/commit/8f3bd70cc78b00986aaf7fc8e9fbd77df05e6b26"><code>8f3bd70</code></a> JUnit reports now interpret Label(owner:X) and set owner to X.</li> <li><a href="https://github.com/onsi/ginkgo/commit/dbaf18fd0af2b798961b08ee9c0a3266d3abadd6"><code>dbaf18f</code></a> Document areas where GinkgoT() behaves differently from testing.T</li> <li><a href="https://github.com/onsi/ginkgo/commit/6f67a147b39873678462615d412cfb0177463bf1"><code>6f67a14</code></a> bugfix(docs): use Unsetenv instead of Clearenv (<a href="https://redirect.github.com/onsi/ginkgo/issues/1337">#1337</a>)</li> <li><a href="https://github.com/onsi/ginkgo/commit/beaf16d17f98f30365a11ff236583d611c094078"><code>beaf16d</code></a> v2.14.0</li> <li>Additional commits viewable in <a href="https://github.com/onsi/ginkgo/compare/v2.13.2...v2.15.0">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> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
