-
Notifications
You must be signed in to change notification settings - Fork 2
fix(deps): update module github.com/onsi/ginkgo/v2 to v2.27.3 #82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
0f8995a to
010537a
Compare
010537a to
0c008aa
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
0c008aa to
4df4b7a
Compare
3a66be8 to
4df4b7a
Compare
4df4b7a to
3948786
Compare
3948786 to
fd493fb
Compare
fd493fb to
4ce2d2b
Compare
4ce2d2b to
f78fedb
Compare
73ae6f6 to
f78fedb
Compare
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
f78fedb to
73ae6f6
Compare
This PR contains the following updates:
v2.24.0→v2.27.3Release Notes
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.27.3Compare Source
2.27.3
Fixes
report exit result in case of failure [
1c9f356]fix data race [
ece19c8]v2.27.2Compare Source
2.27.2
Fixes
a69113a]Maintenance
a99c6e0]f993df5]v2.27.1Compare Source
2.27.1
Fixes
606c1cb]a6463b3]v2.27.0Compare Source
2.27.0
Features
Transforming Nodes during Tree Construction
This release adds support for
NodeArgsTransformers that can be registered withAddTreeConstructionNodeArgsTransformer.These are called during the tree construction phase as nodes are constructed and can modify the node strings and decorators. This enables frameworks built on top of Ginkgo to modify Ginkgo nodes and enforce conventions.
Learn more here.
Spec Prioritization
A new
SpecPriority(int)decorator has been added. Ginkgo will honor priority when ordering specs, ensuring that higher priority specs start running before lower priority specsLearn more here.
Maintenance
1333dae]17ae63e]v2.26.0Compare Source
2.26.0
Features
Ginkgo can now generate json-formatted reports that are compatible with the
go testjson format. Useginkgo --gojson-report=report.go.json. This is not intended to be a replacement for Ginkgo's native json format which is more information rich and better models Ginkgo's test structure semantics.v2.25.3Compare Source
2.25.3
Fixes
f01aed1]v2.25.2Compare Source
2.25.2
Fixes
Add github output group for progress report content
Maintenance
Bump Gomega
v2.25.1Compare Source
2.25.1
Fixes
10866d3]2e42cff]v2.25.0Compare Source
2.25.0
AroundNodeThis release introduces a new decorator to support more complex spec setup usecases.
AroundNoderegisters 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())-funcwill be called before the node is run.AroundNode(func(ctx context.Context) context.Context)-funccan 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)))-ctxis the context for the node andbodyis a function that must be called to run the node. This gives you complete control over what runs before and after the node.Multiple
AroundNodedecorators can be applied to a single node and they will run in the order they are applied.Unlike setup nodes like
BeforeEachandDeferCleanup,AroundNodeis 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 callruntime.LockOSThread()in theAroundNodeto ensure that the node runs on a single thread).Since
AroundNodeallows you to modify the context you can also useAroundNodeto implement shared setup that attaches values to the context.If applied to a container,
AroundNodewill run before every node in the container. Including setup nodes likeBeforeEachandDeferCleanup.AroundNodecan also be applied toRunSpecsto run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.