You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build(deps): Bump github.com/onsi/ginkgo/v2 from 2.10.0 to 2.11.0 (runfinch#456)
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from
2.10.0 to 2.11.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.11.0</h2>
<h2>2.11.0</h2>
<p>In prior versions of Ginkgo specs the CLI filter flags (e.g.
<code>--focus</code>, <code>--label-filter</code>) would
<em>override</em> any programmatic focus. This behavior has proved
surprising and confusing in at least the following ways:</p>
<ul>
<li>users cannot combine programmatic filters and CLI filters to more
efficiently select subsets of tests</li>
<li>CLI filters can override programmatic focus on CI systems resulting
in an exit code of 0 despite the presence of (incorrectly!) committed
focused specs.</li>
</ul>
<p>Going forward Ginkgo will AND all programmatic and CLI filters.
Moreover, the presence of any programmatic focused tests will always
result in a non-zero exit code.</p>
<p>This change is technically a change in Ginkgo's external contract and
may require some users to make changes to successfully adopt.
Specifically: it's possible some users were intentionally using CLI
filters to override programmatic focus. If this is you please open an
issue so we can explore solutions to the underlying problem you are
trying to solve.</p>
<h3>Fixes</h3>
<ul>
<li>Programmatic focus is no longer overwrriten by CLI filters
[d6bba86]</li>
</ul>
<h3>Maintenance</h3>
<ul>
<li>Bump github.com/onsi/gomega from 1.27.7 to 1.27.8 (<a
href="https://redirect.github.com/onsi/ginkgo/issues/1218">#1218</a>)
[4a70a38]</li>
<li>Bump golang.org/x/sys from 0.8.0 to 0.9.0 (<a
href="https://redirect.github.com/onsi/ginkgo/issues/1219">#1219</a>)
[97eda4d]</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.11.0</h2>
<p>In prior versions of Ginkgo specs the CLI filter flags (e.g.
<code>--focus</code>, <code>--label-filter</code>) would
<em>override</em> any programmatic focus. This behavior has proved
surprising and confusing in at least the following ways:</p>
<ul>
<li>users cannot combine programmatic filters and CLI filters to more
efficiently select subsets of tests</li>
<li>CLI filters can override programmatic focus on CI systems resulting
in an exit code of 0 despite the presence of (incorrectly!) committed
focused specs.</li>
</ul>
<p>Going forward Ginkgo will AND all programmatic and CLI filters.
Moreover, the presence of any programmatic focused tests will always
result in a non-zero exit code.</p>
<p>This change is technically a change in Ginkgo's external contract and
may require some users to make changes to successfully adopt.
Specifically: it's possible some users were intentionally using CLI
filters to override programmatic focus. If this is you please open an
issue so we can explore solutions to the underlying problem you are
trying to solve.</p>
<h3>Fixes</h3>
<ul>
<li>Programmatic focus is no longer overwrriten by CLI filters
[d6bba86]</li>
</ul>
<h3>Maintenance</h3>
<ul>
<li>Bump github.com/onsi/gomega from 1.27.7 to 1.27.8 (<a
href="https://redirect.github.com/onsi/ginkgo/issues/1218">#1218</a>)
[4a70a38]</li>
<li>Bump golang.org/x/sys from 0.8.0 to 0.9.0 (<a
href="https://redirect.github.com/onsi/ginkgo/issues/1219">#1219</a>)
[97eda4d]</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/onsi/ginkgo/commit/5c32b2a6408b866b04774abad81eca2274f4fb5b"><code>5c32b2a</code></a>
v2.11.0</li>
<li><a
href="https://github.com/onsi/ginkgo/commit/d6bba86e67d4973f786752a070f69b7732601caa"><code>d6bba86</code></a>
Programmatic focus is no longer overwrriten by CLI filters</li>
<li><a
href="https://github.com/onsi/ginkgo/commit/4a70a38d78ea5f2bca038945b4e49442fb93c7a3"><code>4a70a38</code></a>
Bump github.com/onsi/gomega from 1.27.7 to 1.27.8 (<a
href="https://redirect.github.com/onsi/ginkgo/issues/1218">#1218</a>)</li>
<li><a
href="https://github.com/onsi/ginkgo/commit/97eda4d083fd88e17b9f1c947a24cf0ac5864dce"><code>97eda4d</code></a>
Bump golang.org/x/sys from 0.8.0 to 0.9.0 (<a
href="https://redirect.github.com/onsi/ginkgo/issues/1219">#1219</a>)</li>
<li>See full diff in <a
href="https://github.com/onsi/ginkgo/compare/v2.10.0...v2.11.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>
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4&size=40){kind=avatar}
0 commit comments