dependabot[bot] opened a new pull request, #2177: URL: https://github.com/apache/apisix-ingress-controller/pull/2177
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.13.2 to 2.16.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.16.0</h2> <h2>2.16.0</h2> <h3>Features</h3> <ul> <li>add SpecContext to reporting nodes</li> </ul> <h3>Fixes</h3> <ul> <li>merge coverages instead of combining them (<a href="https://redirect.github.com/onsi/ginkgo/issues/1329">#1329</a>) (<a href="https://redirect.github.com/onsi/ginkgo/issues/1340">#1340</a>) [23f0cc5]</li> <li>core_dsl: disable Getwd() with environment variable (<a href="https://redirect.github.com/onsi/ginkgo/issues/1357">#1357</a>) [cd418b7]</li> </ul> <h3>Maintenance</h3> <ul> <li>docs/index.md: Typo [2cebe8d]</li> <li>fix docs [06de431]</li> <li>chore: test with Go 1.22 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1352">#1352</a>) [898cba9]</li> <li>Bump golang.org/x/tools from 0.16.1 to 0.17.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1336">#1336</a>) [17ae120]</li> <li>Bump golang.org/x/sys from 0.15.0 to 0.16.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1327">#1327</a>) [5a179ed]</li> <li>Bump github.com/go-logr/logr from 1.3.0 to 1.4.1 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1321">#1321</a>) [a1e6b69]</li> <li>Bump github-pages and jekyll-feed in /docs (<a href="https://redirect.github.com/onsi/ginkgo/issues/1351">#1351</a>) [d52951d]</li> <li>Fix docs for handling failures in goroutines (<a href="https://redirect.github.com/onsi/ginkgo/issues/1339">#1339</a>) [4471b2e]</li> </ul> <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> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </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.16.0</h2> <h3>Features</h3> <ul> <li>add SpecContext to reporting nodes</li> </ul> <h3>Fixes</h3> <ul> <li>merge coverages instead of combining them (<a href="https://redirect.github.com/onsi/ginkgo/issues/1329">#1329</a>) (<a href="https://redirect.github.com/onsi/ginkgo/issues/1340">#1340</a>) [23f0cc5]</li> <li>core_dsl: disable Getwd() with environment variable (<a href="https://redirect.github.com/onsi/ginkgo/issues/1357">#1357</a>) [cd418b7]</li> </ul> <h3>Maintenance</h3> <ul> <li>docs/index.md: Typo [2cebe8d]</li> <li>fix docs [06de431]</li> <li>chore: test with Go 1.22 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1352">#1352</a>) [898cba9]</li> <li>Bump golang.org/x/tools from 0.16.1 to 0.17.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1336">#1336</a>) [17ae120]</li> <li>Bump golang.org/x/sys from 0.15.0 to 0.16.0 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1327">#1327</a>) [5a179ed]</li> <li>Bump github.com/go-logr/logr from 1.3.0 to 1.4.1 (<a href="https://redirect.github.com/onsi/ginkgo/issues/1321">#1321</a>) [a1e6b69]</li> <li>Bump github-pages and jekyll-feed in /docs (<a href="https://redirect.github.com/onsi/ginkgo/issues/1351">#1351</a>) [d52951d]</li> <li>Fix docs for handling failures in goroutines (<a href="https://redirect.github.com/onsi/ginkgo/issues/1339">#1339</a>) [4471b2e]</li> </ul> <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> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/onsi/ginkgo/commit/a181ee22f50186b1be81d3d3011a6841518782d2"><code>a181ee2</code></a> v2.16.0</li> <li><a href="https://github.com/onsi/ginkgo/commit/2cebe8d4def1a24d5df12819defbc980a0fcaea2"><code>2cebe8d</code></a> docs/index.md: Typo</li> <li><a href="https://github.com/onsi/ginkgo/commit/881efde71ccc44d0d2ebc02f3641941e143a1c1d"><code>881efde</code></a> update documentation to reflect changes to reporting nodes</li> <li><a href="https://github.com/onsi/ginkgo/commit/c4e219ff5f317e6f0b78e30c2554088ee3ea2f92"><code>c4e219f</code></a> add SpecContext to other reporting nodes and update tests</li> <li><a href="https://github.com/onsi/ginkgo/commit/06de43198fea28d265ee93530424252028f30181"><code>06de431</code></a> fix docs</li> <li><a href="https://github.com/onsi/ginkgo/commit/372d26a2c9cfda920b52f6230cdd2d94f1cdec2e"><code>372d26a</code></a> update docs</li> <li><a href="https://github.com/onsi/ginkgo/commit/fd929c6e27e6b53886f2d76525c97f9f130cb560"><code>fd929c6</code></a> update test description</li> <li><a href="https://github.com/onsi/ginkgo/commit/fed9402d63e0871b76dc390a18e3fa23d8428e92"><code>fed9402</code></a> update documentation.</li> <li><a href="https://github.com/onsi/ginkgo/commit/5ff9d7fafb94f34fa83fbbc29132d1ef60890e19"><code>5ff9d7f</code></a> Add SpecContext to ReportAfterSuite callback body.</li> <li><a href="https://github.com/onsi/ginkgo/commit/9c771cd687800da7a9a6c65c0e447127e6a90548"><code>9c771cd</code></a> Add SpecContext to ReportAfterSuite callback body.</li> <li>Additional commits viewable in <a href="https://github.com/onsi/ginkgo/compare/v2.13.2...v2.16.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]
