chore: Update from ubi8/go-toolset:1.19.13-2 to ubi8/go-toolset:1.20.10-3

[che-bot]

Signed-off-by: Nick Boldt [email protected]

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (7.77.x@5c34a13). Click here to learn what that means.

Additional details and impacted files

@@            Coverage Diff            @@
##             7.77.x     #273   +/-   ##
=========================================
  Coverage          ?   44.31%           
=========================================
  Files             ?       13           
  Lines             ?      519           
  Branches          ?        0           
=========================================
  Hits              ?      230           
  Misses            ?      286           
  Partials          ?        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[amisevsk]

I feel like this should be restricted to 1.19 bugfixes

[nickboldt]

yeah but some CVEs are only fixed in 1.20 and 1.21... so this might be a good thing.

see https://issues.redhat.com/browse/CRW-4374?jql=project%20%3D%20CRW%20AND%20component%20%3D%20%22productization%3A%20security%20%26%20legal%22%20and%20resolution%20is%20null%20and%20text~golang

[nickboldt]

approve, tentatively. Not sure if moving to 1.20 breaks anything... or requires updated go.mod/go.sum files, etc.

[tolusha]

I am against switching builder to 1.20 without switching the whole project to 1.20

[SDawley]

OK I've updated the go deps, go mod etc.
I tested building the rhel.Dockerfile and Dockerfiles and they build, but as to functional testing that would have to be someone else's domain.

[SDawley]

If updating go can be tested, updating to 1.20 is preferable but it can be left out.

Updating UBI8 to the 8.9 version is much more important.