kubernetes-sigs
Bump github.com/onsi/ginkgo/v2 from 2.19.0 to 2.20.2
Bumps github.com/onsi/ginkgo/v2 from 2.19.0 to 2.20.2.
Release notes
Sourced from github.com/onsi/ginkgo/v2's releases.
v2.20.2
2.20.2
Require Go 1.22+
Maintenance
- bump go to v1.22 [a671816]
v2.20.1
2.20.1
Fixes
- make BeSpecEvent duration matcher more forgiving [d6f9640]
v2.20.0
2.20.0
Features
- Add buildvcs flag [be5ab95]
Maintenance
- Add update-deps to makefile [d303d14]
- bump all dependencies [7a50221]
v2.19.1
2.19.1
Fixes
- update supported platforms for race conditions [63c8c30]
- [build] Allow custom name for binaries. [ff41e27]
Maintenance
Changelog
Sourced from github.com/onsi/ginkgo/v2's changelog.
2.20.2
Require Go 1.22+
Maintenance
- bump go to v1.22 [a671816]
2.20.1
Fixes
- make BeSpecEvent duration matcher more forgiving [d6f9640]
2.20.0
Features
- Add buildvcs flag [be5ab95]
Maintenance
- Add update-deps to makefile [d303d14]
- bump all dependencies [7a50221]
2.19.1
Fixes
- update supported platforms for race conditions [63c8c30]
- [build] Allow custom name for binaries. [ff41e27]
Maintenance
Commits
104752fv2.20.2a671816bump go to v1.224ef0afbv2.20.1d6f9640make BeSpecEvent duration matcher more forgiving265b1a0v2.20.0d303d14Add update-deps to makefile7a50221bump all dependenciesbe5ab95Add buildvcs flag224be5bv2.19.176f4e0cbump gomega- 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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign enxebre for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Hi @dependabot[bot]. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.
@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-cluster-api-provider-digitalocean-verify | 437a94c11bedff98e0f563e60570b1bd839472eb | link | true | /test pull-cluster-api-provider-digitalocean-verify |
| pull-cluster-api-provider-digitalocean-test | 437a94c11bedff98e0f563e60570b1bd839472eb | link | true | /test pull-cluster-api-provider-digitalocean-test |
| pull-cluster-api-provider-digitalocean-e2e | 437a94c11bedff98e0f563e60570b1bd839472eb | link | true | /test pull-cluster-api-provider-digitalocean-e2e |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.
A newer version of github.com/onsi/ginkgo/v2 exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.
PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.