flake downloading kustomize, will re-run

Does it make sense to bump ginkgo/gomega here like you did for release-1.23?

Does it make sense to bump ginkgo/gomega here like you did for release-1.23?

yeah we could def do that, though the thought was to be a little more conservative on the older releases since the version changes in those tools was broader/to avoid debugging something unrelated

Codecov Report

Merging #4882 (d4a663e) into release-1.22 (a34c6d5) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           release-1.22    #4882   +/-   ##
=============================================
  Coverage         75.96%   75.96%           
=============================================
  Files               140      140           
  Lines             13102    13102           
=============================================
  Hits               9953     9953           
  Misses             2892     2892           
  Partials            257      257           

Does it make sense to bump ginkgo/gomega here like you did for release-1.23?

yeah we could def do that, though the thought was to be a little more conservative on the older releases since the version changes in those tools was broader/to avoid debugging something unrelated

Fair enough. I see there's no explicit version override for golang.org/x/net so that must be getting bumped as a result of one of the other ones?

Does it make sense to bump ginkgo/gomega here like you did for release-1.23?

yeah we could def do that, though the thought was to be a little more conservative on the older releases since the version changes in those tools was broader/to avoid debugging something unrelated

Fair enough. I see there's no explicit version override for golang.org/x/net so that must be getting bumped as a result of one of the other ones?

yeah the x/net bump makes the x/text bump a no-op