dependabot[bot] opened a new pull request, #1454: URL: https://github.com/apache/apisix-ingress-controller/pull/1454
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.4.0 to 2.5.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.5.0</h2> <h2>2.5.0</h2> <h3>Ginkgo output now includes a timeline-view of the spec</h3> <p>This commit changes Ginkgo's default output. Spec details are now presented as a <strong>timeline</strong> that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.</p> <p>The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node <code>> Enter</code> and <code>< Exit</code> events in the spec timeline.</p> <p>In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using <code>GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)</code></p> <p>Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you <em>may</em> run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.</p> <h3>Features</h3> <ul> <li>Provide details about which timeout expired [0f2fa27]</li> </ul> <h3>Fixes</h3> <ul> <li>Add Support Policy to docs [c70867a]</li> </ul> <h3>Maintenance</h3> <ul> <li>Bump github.com/onsi/gomega from 1.22.1 to 1.23.0 (<a href="https://github-redirect.dependabot.com/onsi/ginkgo/issues/1070";>#1070</a>) [bb3b4e2]</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.5.0</h2> <h3>Ginkgo output now includes a timeline-view of the spec</h3> <p>This commit changes Ginkgo's default output. Spec details are now presented as a <strong>timeline</strong> that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.</p> <p>The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node <code>> Enter</code> and <code>< Exit</code> events in the spec timeline.</p> <p>In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using <code>GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)</code></p> <p>Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you <em>may</em> run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.</p> <h3>Features</h3> <ul> <li>Provide details about which timeout expired [0f2fa27]</li> </ul> <h3>Fixes</h3> <ul> <li>Add Support Policy to docs [c70867a]</li> </ul> <h3>Maintenance</h3> <ul> <li>Bump github.com/onsi/gomega from 1.22.1 to 1.23.0 (<a href="https://github-redirect.dependabot.com/onsi/ginkgo/issues/1070";>#1070</a>) [bb3b4e2]</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/onsi/ginkgo/commit/fdb6c47b1e9f8b9ca8ab479dde7a4bf2a49c45e2";><code>fdb6c47</code></a> v2.5.0</li> <li><a href="https://github.com/onsi/ginkgo/commit/db83f33f1142f246e6984eb82751ddefa2a94594";><code>db83f33</code></a> Ginkgo output now includes a timeline-view of the spec</li> <li><a href="https://github.com/onsi/ginkgo/commit/c70867a9661d9eb6eeb706dd7580bf510a99f35b";><code>c70867a</code></a> Add Support Policy to docs</li> <li><a href="https://github.com/onsi/ginkgo/commit/0f2fa2787054cf7b1f7c32ac3f4548b9e6033864";><code>0f2fa27</code></a> Provide details about which timeout expired</li> <li><a href="https://github.com/onsi/ginkgo/commit/bb3b4e24ec722d121b2e0c738585f915fedd0ba5";><code>bb3b4e2</code></a> Bump github.com/onsi/gomega from 1.22.1 to 1.23.0 (<a href="https://github-redirect.dependabot.com/onsi/ginkgo/issues/1070";>#1070</a>)</li> <li>See full diff in <a href="https://github.com/onsi/ginkgo/compare/v2.4.0...v2.5.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 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]
