deps: bump github.com/onsi/ginkgo/v2 from 2.23.4 to 2.25.3#1879
Merged
matmerr merged 1 commit intoSep 24, 2025
Conversation
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.23.4 to 2.25.3. - [Release notes](https://github.com/onsi/ginkgo/releases) - [Changelog](https://github.com/onsi/ginkgo/blob/master/CHANGELOG.md) - [Commits](onsi/ginkgo@v2.23.4...v2.25.3) --- updated-dependencies: - dependency-name: github.com/onsi/ginkgo/v2 dependency-version: 2.25.3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
area/dependencies
dependabot
Bot
added
area/dependencies
matmerr
approved these changes
Sep 24, 2025
matmerr
deleted the
dependabot/go_modules/github.com/onsi/ginkgo/v2-2.25.3
branch
agrawaliti
pushed a commit
to agrawaliti/retina
that referenced
this pull request
Oct 22, 2025
…#1879) Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.23.4 to 2.25.3. <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.25.3</h2> <h2>2.25.3</h2> <h3>Fixes</h3> <ul> <li>emit --github-output group only for progress report itself [f01aed1]</li> </ul> <h2>v2.25.2</h2> <h2>2.25.2</h2> <h3>Fixes</h3> <p>Add github output group for progress report content</p> <h3>Maintenance</h3> <p>Bump Gomega</p> <h2>v2.25.1</h2> <h2>2.25.1</h2> <h3>Fixes</h3> <ul> <li>fix(types): ignore nameless nodes on FullText() [10866d3]</li> <li>chore: fix some CodeQL warnings [2e42cff]</li> </ul> <h2>v2.25.0</h2> <h2>2.25.0</h2> <h3><code>AroundNode</code></h3> <p>This release introduces a new decorator to support more complex spec setup usecases.</p> <p><code>AroundNode</code> registers a function that runs before each individual node. This is considered a more advanced decorator.</p> <p>Please read the <a href="https://onsi.github.io/ginkgo/#advanced-around-node">docs</a> for more information and some examples.</p> <p>Allowed signatures:</p> <ul> <li><code>AroundNode(func())</code> - <code>func</code> will be called before the node is run.</li> <li><code>AroundNode(func(ctx context.Context) context.Context)</code> - <code>func</code> can wrap the passed in context and return a new one which will be passed on to the node.</li> <li><code>AroundNode(func(ctx context.Context, body func(ctx context.Context)))</code> - <code>ctx</code> is the context for the node and <code>body</code> is a function that must be called to run the node. This gives you complete control over what runs before and after the node.</li> </ul> <p>Multiple <code>AroundNode</code> decorators can be applied to a single node and they will run in the order they are applied.</p> <p>Unlike setup nodes like <code>BeforeEach</code> and <code>DeferCleanup</code>, <code>AroundNode</code> is guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can call <code>runtime.LockOSThread()</code> in the <code>AroundNode</code> to ensure that the node runs on a single thread).</p> <p>Since <code>AroundNode</code> allows you to modify the context you can also use <code>AroundNode</code> to implement shared setup that attaches values to the context.</p> <p>If applied to a container, <code>AroundNode</code> will run before every node in the container. Including setup nodes like <code>BeforeEach</code> and <code>DeferCleanup</code>.</p> <p><code>AroundNode</code> can also be applied to <code>RunSpecs</code> to run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.</p> <!-- 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.25.3</h2> <h3>Fixes</h3> <ul> <li>emit --github-output group only for progress report itself [f01aed1]</li> </ul> <h2>2.25.2</h2> <h3>Fixes</h3> <p>Add github output group for progress report content</p> <h3>Maintenance</h3> <p>Bump Gomega</p> <h2>2.25.1</h2> <h3>Fixes</h3> <ul> <li>fix(types): ignore nameless nodes on FullText() [10866d3]</li> <li>chore: fix some CodeQL warnings [2e42cff]</li> </ul> <h2>2.25.0</h2> <h3><code>AroundNode</code></h3> <p>This release introduces a new decorator to support more complex spec setup usecases.</p> <p><code>AroundNode</code> registers a function that runs before each individual node. This is considered a more advanced decorator.</p> <p>Please read the <a href="https://onsi.github.io/ginkgo/#advanced-around-node">docs</a> for more information and some examples.</p> <p>Allowed signatures:</p> <ul> <li><code>AroundNode(func())</code> - <code>func</code> will be called before the node is run.</li> <li><code>AroundNode(func(ctx context.Context) context.Context)</code> - <code>func</code> can wrap the passed in context and return a new one which will be passed on to the node.</li> <li><code>AroundNode(func(ctx context.Context, body func(ctx context.Context)))</code> - <code>ctx</code> is the context for the node and <code>body</code> is a function that must be called to run the node. This gives you complete control over what runs before and after the node.</li> </ul> <p>Multiple <code>AroundNode</code> decorators can be applied to a single node and they will run in the order they are applied.</p> <p>Unlike setup nodes like <code>BeforeEach</code> and <code>DeferCleanup</code>, <code>AroundNode</code> is guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can call <code>runtime.LockOSThread()</code> in the <code>AroundNode</code> to ensure that the node runs on a single thread).</p> <p>Since <code>AroundNode</code> allows you to modify the context you can also use <code>AroundNode</code> to implement shared setup that attaches values to the context.</p> <p>If applied to a container, <code>AroundNode</code> will run before every node in the container. Including setup nodes like <code>BeforeEach</code> and <code>DeferCleanup</code>.</p> <p><code>AroundNode</code> can also be applied to <code>RunSpecs</code> to run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.</p> <h2>2.24.0</h2> <h3>Features</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/onsi/ginkgo/commit/ee2c0cd1b8580c45c33f0f7c7a848b75e8056ebe"><code>ee2c0cd</code></a> v2.25.3</li> <li><a href="https://github.com/onsi/ginkgo/commit/f01aed18626198447da5a63a5989e2d26c7a3746"><code>f01aed1</code></a> emit --github-output group only for progress report itself</li> <li><a href="https://github.com/onsi/ginkgo/commit/df6d7552b350099017fbf486a24200fd44853c52"><code>df6d755</code></a> v2.25.2</li> <li><a href="https://github.com/onsi/ginkgo/commit/0ad3c4f51aedca5eb2d91b309bafe41c33ad24a2"><code>0ad3c4f</code></a> bump gomega</li> <li><a href="https://github.com/onsi/ginkgo/commit/83e2d4a0c8a91dc2008f26e37b108f0cd89cfb99"><code>83e2d4a</code></a> add --github-output group for progress report content</li> <li><a href="https://github.com/onsi/ginkgo/commit/1ec91144e3ba4dec32f0aa8b6c50888908a1697b"><code>1ec9114</code></a> v2.25.1</li> <li><a href="https://github.com/onsi/ginkgo/commit/2e42cff58e53535fe3a0904941393089f7ad9ff2"><code>2e42cff</code></a> chore: fix some CodeQL warnings</li> <li><a href="https://github.com/onsi/ginkgo/commit/10866d3ce04a0283d7d9484366f082a07e46b311"><code>10866d3</code></a> fix(types): ignore nameless nodes on FullText()</li> <li><a href="https://github.com/onsi/ginkgo/commit/fcc0e74deeb1be682ffa7b56e6567183643798dd"><code>fcc0e74</code></a> v2.25.0</li> <li><a href="https://github.com/onsi/ginkgo/commit/79e35c958f43978a5ef16d3ab029dbdaade8c14c"><code>79e35c9</code></a> tidy up docs</li> <li>Additional commits viewable in <a href="https://github.com/onsi/ginkgo/compare/v2.23.4...v2.25.3">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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
mereta
pushed a commit
that referenced
this pull request
Dec 2, 2025
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.23.4 to 2.25.3. <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.25.3</h2> <h2>2.25.3</h2> <h3>Fixes</h3> <ul> <li>emit --github-output group only for progress report itself [f01aed1]</li> </ul> <h2>v2.25.2</h2> <h2>2.25.2</h2> <h3>Fixes</h3> <p>Add github output group for progress report content</p> <h3>Maintenance</h3> <p>Bump Gomega</p> <h2>v2.25.1</h2> <h2>2.25.1</h2> <h3>Fixes</h3> <ul> <li>fix(types): ignore nameless nodes on FullText() [10866d3]</li> <li>chore: fix some CodeQL warnings [2e42cff]</li> </ul> <h2>v2.25.0</h2> <h2>2.25.0</h2> <h3><code>AroundNode</code></h3> <p>This release introduces a new decorator to support more complex spec setup usecases.</p> <p><code>AroundNode</code> registers a function that runs before each individual node. This is considered a more advanced decorator.</p> <p>Please read the <a href="https://onsi.github.io/ginkgo/#advanced-around-node">docs</a> for more information and some examples.</p> <p>Allowed signatures:</p> <ul> <li><code>AroundNode(func())</code> - <code>func</code> will be called before the node is run.</li> <li><code>AroundNode(func(ctx context.Context) context.Context)</code> - <code>func</code> can wrap the passed in context and return a new one which will be passed on to the node.</li> <li><code>AroundNode(func(ctx context.Context, body func(ctx context.Context)))</code> - <code>ctx</code> is the context for the node and <code>body</code> is a function that must be called to run the node. This gives you complete control over what runs before and after the node.</li> </ul> <p>Multiple <code>AroundNode</code> decorators can be applied to a single node and they will run in the order they are applied.</p> <p>Unlike setup nodes like <code>BeforeEach</code> and <code>DeferCleanup</code>, <code>AroundNode</code> is guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can call <code>runtime.LockOSThread()</code> in the <code>AroundNode</code> to ensure that the node runs on a single thread).</p> <p>Since <code>AroundNode</code> allows you to modify the context you can also use <code>AroundNode</code> to implement shared setup that attaches values to the context.</p> <p>If applied to a container, <code>AroundNode</code> will run before every node in the container. Including setup nodes like <code>BeforeEach</code> and <code>DeferCleanup</code>.</p> <p><code>AroundNode</code> can also be applied to <code>RunSpecs</code> to run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.</p> <!-- 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.25.3</h2> <h3>Fixes</h3> <ul> <li>emit --github-output group only for progress report itself [f01aed1]</li> </ul> <h2>2.25.2</h2> <h3>Fixes</h3> <p>Add github output group for progress report content</p> <h3>Maintenance</h3> <p>Bump Gomega</p> <h2>2.25.1</h2> <h3>Fixes</h3> <ul> <li>fix(types): ignore nameless nodes on FullText() [10866d3]</li> <li>chore: fix some CodeQL warnings [2e42cff]</li> </ul> <h2>2.25.0</h2> <h3><code>AroundNode</code></h3> <p>This release introduces a new decorator to support more complex spec setup usecases.</p> <p><code>AroundNode</code> registers a function that runs before each individual node. This is considered a more advanced decorator.</p> <p>Please read the <a href="https://onsi.github.io/ginkgo/#advanced-around-node">docs</a> for more information and some examples.</p> <p>Allowed signatures:</p> <ul> <li><code>AroundNode(func())</code> - <code>func</code> will be called before the node is run.</li> <li><code>AroundNode(func(ctx context.Context) context.Context)</code> - <code>func</code> can wrap the passed in context and return a new one which will be passed on to the node.</li> <li><code>AroundNode(func(ctx context.Context, body func(ctx context.Context)))</code> - <code>ctx</code> is the context for the node and <code>body</code> is a function that must be called to run the node. This gives you complete control over what runs before and after the node.</li> </ul> <p>Multiple <code>AroundNode</code> decorators can be applied to a single node and they will run in the order they are applied.</p> <p>Unlike setup nodes like <code>BeforeEach</code> and <code>DeferCleanup</code>, <code>AroundNode</code> is guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can call <code>runtime.LockOSThread()</code> in the <code>AroundNode</code> to ensure that the node runs on a single thread).</p> <p>Since <code>AroundNode</code> allows you to modify the context you can also use <code>AroundNode</code> to implement shared setup that attaches values to the context.</p> <p>If applied to a container, <code>AroundNode</code> will run before every node in the container. Including setup nodes like <code>BeforeEach</code> and <code>DeferCleanup</code>.</p> <p><code>AroundNode</code> can also be applied to <code>RunSpecs</code> to run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.</p> <h2>2.24.0</h2> <h3>Features</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/onsi/ginkgo/commit/ee2c0cd1b8580c45c33f0f7c7a848b75e8056ebe"><code>ee2c0cd</code></a> v2.25.3</li> <li><a href="https://github.com/onsi/ginkgo/commit/f01aed18626198447da5a63a5989e2d26c7a3746"><code>f01aed1</code></a> emit --github-output group only for progress report itself</li> <li><a href="https://github.com/onsi/ginkgo/commit/df6d7552b350099017fbf486a24200fd44853c52"><code>df6d755</code></a> v2.25.2</li> <li><a href="https://github.com/onsi/ginkgo/commit/0ad3c4f51aedca5eb2d91b309bafe41c33ad24a2"><code>0ad3c4f</code></a> bump gomega</li> <li><a href="https://github.com/onsi/ginkgo/commit/83e2d4a0c8a91dc2008f26e37b108f0cd89cfb99"><code>83e2d4a</code></a> add --github-output group for progress report content</li> <li><a href="https://github.com/onsi/ginkgo/commit/1ec91144e3ba4dec32f0aa8b6c50888908a1697b"><code>1ec9114</code></a> v2.25.1</li> <li><a href="https://github.com/onsi/ginkgo/commit/2e42cff58e53535fe3a0904941393089f7ad9ff2"><code>2e42cff</code></a> chore: fix some CodeQL warnings</li> <li><a href="https://github.com/onsi/ginkgo/commit/10866d3ce04a0283d7d9484366f082a07e46b311"><code>10866d3</code></a> fix(types): ignore nameless nodes on FullText()</li> <li><a href="https://github.com/onsi/ginkgo/commit/fcc0e74deeb1be682ffa7b56e6567183643798dd"><code>fcc0e74</code></a> v2.25.0</li> <li><a href="https://github.com/onsi/ginkgo/commit/79e35c958f43978a5ef16d3ab029dbdaade8c14c"><code>79e35c9</code></a> tidy up docs</li> <li>Additional commits viewable in <a href="https://github.com/onsi/ginkgo/compare/v2.23.4...v2.25.3">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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps github.com/onsi/ginkgo/v2 from 2.23.4 to 2.25.3.
Release notes
Sourced from github.com/onsi/ginkgo/v2's releases.
... (truncated)
Changelog
Sourced from github.com/onsi/ginkgo/v2's changelog.
... (truncated)
Commits
ee2c0cdv2.25.3f01aed1emit --github-output group only for progress report itselfdf6d755v2.25.20ad3c4fbump gomega83e2d4aadd --github-output group for progress report content1ec9114v2.25.12e42cffchore: fix some CodeQL warnings10866d3fix(types): ignore nameless nodes on FullText()fcc0e74v2.25.079e35c9tidy up docsDependabot 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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)