Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 18, 2025

This PR contains the following updates:

Package Change Age Confidence
github.com/onsi/ginkgo/v2 v2.23.4 -> v2.25.2 age confidence

Release Notes

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

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
Maintenance

Numerous dependency bumps and documentation fixes


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 renovate bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Aug 18, 2025
@renovate renovate bot requested a review from a team as a code owner August 18, 2025 19:36
@renovate renovate bot enabled auto-merge (squash) August 18, 2025 19:36
@renovate
Copy link
Contributor Author

renovate bot commented Aug 18, 2025

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

  • 8 additional dependencies were updated

Details:

Package Change
github.com/onsi/gomega v1.37.0 -> v1.38.2
golang.org/x/tools v0.33.0 -> v0.36.0
golang.org/x/mod v0.25.0 -> v0.27.0
golang.org/x/net v0.41.0 -> v0.43.0
golang.org/x/sync v0.15.0 -> v0.16.0
golang.org/x/sys v0.33.0 -> v0.35.0
golang.org/x/text v0.26.0 -> v0.28.0
google.golang.org/protobuf v1.36.6 -> v1.36.7
File name: tests/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

Details:

Package Change
github.com/onsi/gomega v1.37.0 -> v1.38.2
golang.org/x/crypto v0.39.0 -> v0.41.0
golang.org/x/net v0.41.0 -> v0.43.0
golang.org/x/sys v0.33.0 -> v0.35.0
golang.org/x/text v0.26.0 -> v0.28.0
golang.org/x/tools v0.33.0 -> v0.36.0
google.golang.org/protobuf v1.36.6 -> v1.36.7

@renovate renovate bot changed the title Update module github.com/onsi/ginkgo/v2 to v2.24.0 Update module github.com/onsi/ginkgo/v2 to v2.25.0 Aug 21, 2025
@renovate renovate bot force-pushed the renovate/github.com-onsi-ginkgo-v2-2.x branch 2 times, most recently from c87ea80 to 4480246 Compare August 22, 2025 05:56
@renovate renovate bot changed the title Update module github.com/onsi/ginkgo/v2 to v2.25.0 Update module github.com/onsi/ginkgo/v2 to v2.25.1 Aug 22, 2025
@renovate renovate bot force-pushed the renovate/github.com-onsi-ginkgo-v2-2.x branch from 4480246 to 7da18d2 Compare August 28, 2025 22:59
@renovate renovate bot changed the title Update module github.com/onsi/ginkgo/v2 to v2.25.1 Update module github.com/onsi/ginkgo/v2 to v2.25.2 Aug 28, 2025
| datasource | package                   | from    | to      |
| ---------- | ------------------------- | ------- | ------- |
| go         | github.com/onsi/ginkgo/v2 | v2.23.4 | v2.25.2 |


Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/github.com-onsi-ginkgo-v2-2.x branch from 7da18d2 to f453de7 Compare September 2, 2025 14:41
@renovate renovate bot merged commit 284ec6d into main Sep 2, 2025
15 checks passed
@renovate renovate bot deleted the renovate/github.com-onsi-ginkgo-v2-2.x branch September 2, 2025 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update Go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants