Update module github.com/onsi/ginkgo/v2 to v2.25.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/onsi/ginkgo/v2	v2.23.0 -> v2.25.3

---

Release Notes

onsi/ginkgo (github.com/onsi/ginkgo/v2)

v2.25.3

Compare Source

2.25.3

Fixes

• emit --github-output group only for progress report itself [f01aed1]

v2.25.2

Compare Source

2.25.2

Fixes

Add github output group for progress report content

Maintenance

Bump Gomega

v2.25.1

Compare Source

2.25.1

Fixes

• fix(types): ignore nameless nodes on FullText() [10866d3]
• chore: fix some CodeQL warnings [2e42cff]

v2.25.0

Compare Source

2.25.0

AroundNode

This release introduces a new decorator to support more complex spec setup usecases.

AroundNode registers a function that runs before each individual node. This is considered a more advanced decorator.

Please read the docs for more information and some examples.

Allowed signatures:

• AroundNode(func()) - func will be called before the node is run.
• AroundNode(func(ctx context.Context) context.Context) - func can wrap the passed in context and return a new one which will be passed on to the node.
• AroundNode(func(ctx context.Context, body func(ctx context.Context))) - ctx is the context for the node and body is a function that must be called to run the node. This gives you complete control over what runs before and after the node.

Multiple AroundNode decorators can be applied to a single node and they will run in the order they are applied.

Unlike setup nodes like BeforeEach and DeferCleanup, AroundNode 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 runtime.LockOSThread() in the AroundNode to ensure that the node runs on a single thread).

Since AroundNode allows you to modify the context you can also use AroundNode to implement shared setup that attaches values to the context.

If applied to a container, AroundNode will run before every node in the container. Including setup nodes like BeforeEach and DeferCleanup.

AroundNode can also be applied to RunSpecs to run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.

v2.24.0

Compare Source

2.24.0

Features

Specs can now be decorated with (e.g.) SemVerConstraint("2.1.0") and ginkgo --sem-ver-filter="2.1.1" will only run constrained specs that match the requested version. Learn more in the docs here! Thanks to @​Icarus9913 for the PR.

Fixes

• remove -o from run command [3f5d379]. fixes #​1582

Maintenance

Numerous dependency bumps and documentation fixes

v2.23.4

Compare Source

2.23.4

Prior to this release Ginkgo would compute the incorrect number of available CPUs when running with -p in a linux container. Thanks to @​emirot for the fix!

Features

• Add automaxprocs for using CPUQuota [2b9c428]

Fixes

• clarify gotchas about -vet flag [1f59d07]

Maintenance

• bump dependencies [2d134d5]

v2.23.3

Compare Source

2.23.3

Fixes

• allow - as a standalone argument [cfcc1a5]
• Bug Fix: Add GinkoTBWrapper.Chdir() and GinkoTBWrapper.Context() [feaf292]
• ignore exit code for symbol test on linux [88e2282]

v2.23.2

Compare Source

2.23.2

🎉🎉🎉

At long last, some long-standing performance gaps between ginkgo and go test have been resolved!

Ginkgo operates by running go test -c to generate test binaries, and then running those binaries. It turns out that the compilation step of go test -c is slower than go test's compilation step because go test strips out debug symbols (ldflags=-w) whereas go test -c does not.

Ginkgo now passes the appropriate ldflags to go test -c when running specs to strip out symbols. This is only done when it is safe to do so and symbols are preferred when profiling is enabled and when ginkgo build is called explicitly.

This, coupled, with the instructions for disabling XProtect on MacOS yields a much better performance experience with Ginkgo.

v2.23.1

Compare Source

2.23.1

🚨 For users on MacOS 🚨

A long-standing Ginkgo performance issue on MacOS seems to be due to mac's antimalware XProtect. You can follow the instructions here to disable it in your terminal. Doing so sped up Ginkgo's own test suite from 1m8s to 47s.

Fixes

Ginkgo's CLI is now a bit clearer if you pass flags in incorrectly:

• make it clearer that you need to pass a filename to the various profile flags, not an absolute directory [a0e52ff]
• emit an error and exit if the ginkgo invocation includes flags after positional arguments [b799d8d]

This might cause existing CI builds to fail. If so then it's likely that your CI build was misconfigured and should be corrected. Open an issue if you need help.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-6f2cda52

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-69dd0c01

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-93d8d6b7

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 9 additional dependencies were updated

Details:

Package	Change
github.com/onsi/gomega	v1.36.2 -> v1.38.2
golang.org/x/sync	v0.12.0 -> v0.16.0
github.com/google/pprof	v0.0.0-20250317173921-a4b03ec1a45e -> v0.0.0-20250403155104-27863c87afa6
golang.org/x/net	v0.37.0 -> v0.43.0
golang.org/x/sys	v0.31.0 -> v0.35.0
golang.org/x/term	v0.30.0 -> v0.34.0
golang.org/x/text	v0.23.0 -> v0.28.0
golang.org/x/tools	v0.31.0 -> v0.36.0
google.golang.org/protobuf	v1.36.5 -> v1.36.7

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-e8ba02fc

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-a00cc42a

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-8299b8d3

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-b589bb9e

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-a9f45f82

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-87e8c175

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:0.0.6-SNAPSHOT-PR-52-0e44ebde

[github-actions]

@renovate[bot] Image is available for testing. docker pull ghcr.io/stakater/uptimeguardian:v0.0.6-SNAPSHOT-PR-52-4ec940ce