Bump the go-version-updates group across 3 directories with 2 updates
Type: Pull Request
State: Open
Association: Contributor
Comments: 0
(4 months ago)
(4 months ago)
dependencies go
Bumps the go-version-updates group with 2 updates in the /auto-discovery/cloud-aws directory: github.com/onsi/ginkgo/v2 and github.com/onsi/gomega.
Bumps the go-version-updates group with 1 update in the /auto-discovery/kubernetes directory: github.com/onsi/gomega.
Bumps the go-version-updates group with 1 update in the /operator directory: github.com/onsi/gomega.
Updates github.com/onsi/ginkgo/v2 from 2.23.4 to 2.25.1
Release notes
Sourced from github.com/onsi/ginkgo/v2's releases.
v2.25.1
2.25.1
Fixes
- fix(types): ignore nameless nodes on FullText() [10866d3]
- chore: fix some CodeQL warnings [2e42cff]
v2.25.0
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.v2.24.0
2.24.0
Features
Specs can now be decorated with (e.g.)
SemVerConstraint("2.1.0")andginkgo --sem-ver-filter="2.1.1"will only run constrained specs that match the requested version. Learn more in the docs here! Thanks to@Icarus9913for the PR.Fixes
- remove -o from run command [3f5d379]. fixes #1582
Maintenance
Numerous dependency bumps and documentation fixes
Changelog
Sourced from github.com/onsi/ginkgo/v2's changelog.
2.25.1
Fixes
- fix(types): ignore nameless nodes on FullText() [10866d3]
- chore: fix some CodeQL warnings [2e42cff]
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.2.24.0
Features
Specs can now be decorated with (e.g.)
SemVerConstraint("2.1.0")andginkgo --sem-ver-filter="2.1.1"will only run constrained specs that match the requested version. Learn more in the docs here! Thanks to@Icarus9913for the PR.Fixes
- remove -o from run command [3f5d379]. fixes #1582
Maintenance
Numerous dependency bumps and documentation fixes
Commits
1ec9114v2.25.12e42cffchore: fix some CodeQL warnings10866d3fix(types): ignore nameless nodes on FullText()fcc0e74v2.25.079e35c9tidy up docs6fef07cDocument AroundNode665e7baAroundNode supports simpler signatures tood41f01eAroundNode - preview3d9dae2v2.24.03f5d379remove -o from run command- Additional commits viewable in compare view
Updates github.com/onsi/gomega from 1.38.0 to 1.38.1
Release notes
Sourced from github.com/onsi/gomega's releases.
v1.38.1
1.38.1
Fixes
Numerous minor fixes and dependency bumps
Changelog
Sourced from github.com/onsi/gomega's changelog.
1.38.1
Fixes
Numerous minor fixes and dependency bumps
Commits
c36e89av1.38.192eaa57go mod tidyb9ed3cddeprecate CompileTest*2a5bf77fix invalid fmt.Errorf3e9e385bump ginkgo7f37abeReplacegopkg.in/yaml.v3withgo.yaml.in/yaml/v369e4761fix(async_assertion): use correct error in errors.As95737c0Bump golang.org/x/net from 0.41.0 to 0.43.0 (#856)91b20eachore: fix Go vet issue with Go 1.156823587Bump nokogiri from 1.18.8 to 1.18.9 in /docs (#854)- Additional commits viewable in compare view
Updates github.com/onsi/gomega from 1.38.0 to 1.38.1
Release notes
Sourced from github.com/onsi/gomega's releases.
v1.38.1
1.38.1
Fixes
Numerous minor fixes and dependency bumps
Changelog
Sourced from github.com/onsi/gomega's changelog.
1.38.1
Fixes
Numerous minor fixes and dependency bumps
Commits
c36e89av1.38.192eaa57go mod tidyb9ed3cddeprecate CompileTest*2a5bf77fix invalid fmt.Errorf3e9e385bump ginkgo7f37abeReplacegopkg.in/yaml.v3withgo.yaml.in/yaml/v369e4761fix(async_assertion): use correct error in errors.As95737c0Bump golang.org/x/net from 0.41.0 to 0.43.0 (#856)91b20eachore: fix Go vet issue with Go 1.156823587Bump nokogiri from 1.18.8 to 1.18.9 in /docs (#854)- Additional commits viewable in compare view
Updates github.com/onsi/gomega from 1.38.0 to 1.38.1
Release notes
Sourced from github.com/onsi/gomega's releases.
v1.38.1
1.38.1
Fixes
Numerous minor fixes and dependency bumps
Changelog
Sourced from github.com/onsi/gomega's changelog.
1.38.1
Fixes
Numerous minor fixes and dependency bumps
Commits
c36e89av1.38.192eaa57go mod tidyb9ed3cddeprecate CompileTest*2a5bf77fix invalid fmt.Errorf3e9e385bump ginkgo7f37abeReplacegopkg.in/yaml.v3withgo.yaml.in/yaml/v369e4761fix(async_assertion): use correct error in errors.As95737c0Bump golang.org/x/net from 0.41.0 to 0.43.0 (#856)91b20eachore: fix Go vet issue with Go 1.156823587Bump nokogiri from 1.18.8 to 1.18.9 in /docs (#854)- Additional commits viewable in compare view
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 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions
Pull Request Statistics
1
6
+109
-100
Package Dependencies
Technical Details
| ID: | 5757785 |
| UUID: | 2772770091 |
| Node ID: | PR_kwDOBM-Q_c6lRR0r |
| Host: | GitHub |
| Repository: | secureCodeBox/secureCodeBox |
| Merge State: | Unknown |