update ginkgo and yamllint

[strongjz]

No description provided.

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[Gacko]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gacko, strongjz

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:

• images/OWNERS [strongjz]

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

[longwuyuan]

Is it because of a branch ? (some places have ginkgo 2.17.1 and this PR sets ginkgo v2.13.1 @strongjz @Gacko

[longwuyuan]

https://github.com/search?q=repo%3Astrongjz%2Fingress-nginx+2.17.1&type=code

[Gacko]

This merges to release-1.9 and I think it's a bit more complicated to update everything to v2.17.1 there.

[strongjz]

im not too concerned for the testing tool version, this is to get golang bumped to 1.22.2 to remove a CVE.

[longwuyuan]

understood