Bump github.com/onsi/gomega from 1.18.1 to 1.19.0

[dependabot]

Bumps github.com/onsi/gomega from 1.18.1 to 1.19.0.

Release notes

Sourced from github.com/onsi/gomega's releases.

v1.19.0

Features

• New HaveEach matcher to ensure that each and every element in an array, slice, or map satisfies the passed in matcher. (#523) [9fc2ae2] (#524) [c8ba582]
• Users can now wrap the Gomega interface to implement custom behavior on each assertion. (#521) [1f2e714]
• ContainElement now accepts an additional pointer argument. Elements that satisfy the matcher are stored in the pointer enabling developers to easily add subsequent, more detailed, assertions against the matching element. (#527) [1a4e27f]

Fixes

• update RELEASING instructions to match ginkgo [0917cde]
• Bump github.com/onsi/ginkgo/v2 from 2.0.0 to 2.1.3 (#519) [49ab4b0]
• Fix CVE-2021-38561 (#534) [f1b4456]
• Fix max number of samples in experiments on non-64-bit systems. (#528) [1c84497]
• Remove dependency on ginkgo v1.16.4 (#530) [4dea8d5]
• Fix for Go 1.18 (#532) [56d2a29]
• Document precendence of timeouts (#533) [b607941]

Changelog

Sourced from github.com/onsi/gomega's changelog.

1.19.0

Features

• New HaveEach matcher to ensure that each and every element in an array, slice, or map satisfies the passed in matcher. (#523) [9fc2ae2] (#524) [c8ba582]
• Users can now wrap the Gomega interface to implement custom behavior on each assertion. (#521) [1f2e714]
• ContainElement now accepts an additional pointer argument. Elements that satisfy the matcher are stored in the pointer enabling developers to easily add subsequent, more detailed, assertions against the matching element. (#527) [1a4e27f]

Fixes

• update RELEASING instructions to match ginkgo [0917cde]
• Bump github.com/onsi/ginkgo/v2 from 2.0.0 to 2.1.3 (#519) [49ab4b0]
• Fix CVE-2021-38561 (#534) [f1b4456]
• Fix max number of samples in experiments on non-64-bit systems. (#528) [1c84497]
• Remove dependency on ginkgo v1.16.4 (#530) [4dea8d5]
• Fix for Go 1.18 (#532) [56d2a29]
• Document precendence of timeouts (#533) [b607941]

Commits

• 3143ff4 v1.19.0
• 0917cde update RELEASING instructions to match ginkgo
• 49ab4b0 Bump github.com/onsi/ginkgo/v2 from 2.0.0 to 2.1.3 (#519)
• f1b4456 Fix CVE-2021-38561 (#534)
• 1c84497 Fix max number of samples in experiments on non-64-bit systems. (#528)
• 4dea8d5 Remove dependency on ginkgo v1.16.4 (#530)
• 1a4e27f Feature/525 return findings for ContainElement (#527)
• 1f2e714 allow users to wrap the Gomega interface (#521)
• 56d2a29 Fix for Go 1.18 (#532)
• b607941 Document precendence of timeouts (#533)
• 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[k8s-ci-robot]

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/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, dependabot[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [cpanato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment