Update module github.com/onsi/gomega to v1.26.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github.com/onsi/gomega	require	minor	v1.24.1 -> v1.26.0

---

Release Notes

onsi/gomega

v1.26.0

Compare Source

1.26.0

Features

• When a polled function returns an error, keep track of the actual and report on the matcher state of the last non-errored actual [21f3090]
• improve eventually failure message output [c530fb3]

Fixes

• fix several documentation spelling issues [e2eff1f]

v1.25.0

Compare Source

1.25.0

Features

• add MustPassRepeatedly(int) to asyncAssertion (#​619) [4509f72]
• compare unwrapped errors using DeepEqual (#​617) [aaeaa5d]

Maintenance

• Bump golang.org/x/net from 0.4.0 to 0.5.0 (#​614) [c7cfea4]
• Bump github.com/onsi/ginkgo/v2 from 2.6.1 to 2.7.0 (#​615) [71b8adb]
• Docs: Fix typo "MUltiple" -> "Multiple" (#​616) [9351dda]
• clean up go.sum [cd1dc1d]

v1.24.2

Compare Source

1.24.2

Fixes

• Correctly handle assertion failure panics for eventually/consistnetly "g Gomega"s in a goroutine [78f1660]
• docs:Fix typo "you an" -> "you can" (#​607) [3187c1f]
• fixes issue #​600 (#​606) [808d192]

Maintenance

• Bump golang.org/x/net from 0.2.0 to 0.4.0 (#​611) [6ebc0bf]
• Bump nokogiri from 1.13.9 to 1.13.10 in /docs (#​612) [258cfc8]
• Bump github.com/onsi/ginkgo/v2 from 2.5.0 to 2.5.1 (#​609) [e6c3eb9]

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[openshift-ci]

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a openstack-k8s-operators 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.

[gibizer]

/ok-to-test

[gibizer]

/lgtm

[gibizer]

/approved

[gibizer]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gibizer, renovate[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 [gibizer]

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

[gibizer]

/lgtm