chore(deps): update module github.com/onsi/ginkgo/v2 to v2.23.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/onsi/ginkgo/v2	v2.22.2 -> v2.23.4

---

Release Notes

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

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.

v2.23.0

Compare Source

2.23.0

Ginkgo 2.23.0 adds a handful of methods to GinkgoT() to make it compatible with the testing.TB interface in Go 1.24. GinkgoT().Context(), in particular, is a useful shorthand for generating a new context that will clean itself up in a DeferCleanup(). This has subtle behavior differences from the golang implementation but should make sense in a Ginkgo... um... context.

Features

• bump to go 1.24.0 - support new testing.TB methods and add a test to cover testing.TB regressions [37a511b]

Fixes

• fix edge case where build -o is pointing at an explicit file, not a directory [7556a86]
• Fix binary paths when precompiling multiple suites. [4df06c6]

Maintenance

• Fix: Correct Markdown list rendering in MIGRATING_TO_V2.md [cbcf39a]
• docs: fix test workflow badge (#​1512) [9b261ff]
• Bump golang.org/x/net in /integration/_fixtures/version_mismatch_fixture (#​1516) [00f19c8]
• Bump golang.org/x/tools from 0.28.0 to 0.30.0 (#​1515) [e98a4df]
• Bump activesupport from 6.0.6.1 to 6.1.7.5 in /docs (#​1504) [60cc4e2]
• Bump github-pages from 231 to 232 in /docs (#​1447) [fea6f2d]
• Bump rexml from 3.2.8 to 3.3.9 in /docs (#​1497) [31d7813]
• Bump webrick from 1.8.1 to 1.9.1 in /docs (#​1501) [fc3bbd6]
• Code linting (#​1500) [aee0d56]
• change interface{} to any (#​1502) [809a710]

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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.

[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):

• 7 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.22.0 -> 1.24.1
golang.org/x/crypto	v0.31.0 -> v0.33.0
golang.org/x/net	v0.33.0 -> v0.35.0
golang.org/x/sync	v0.10.0 -> v0.11.0
golang.org/x/sys	v0.28.0 -> v0.30.0
golang.org/x/term	v0.27.0 -> v0.29.0
golang.org/x/text	v0.21.0 -> v0.22.0
golang.org/x/tools	v0.28.0 -> v0.30.0

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum

Command failed: go get -d -t ./...
go: module github.com/onsi/ginkgo/v2@v2.23.4 requires go >= 1.23.0; switching to go1.23.9
go: downloading go1.23.9 (linux/amd64)
go: download go1.23.9: golang.org/toolchain@v0.0.1-go1.23.9.linux-amd64: verifying module: checksum database disabled by GOSUMDB=off