Description of problem: If CI is building testing and shipping in 1.13 so should we. Currently, this reflects 1.12. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: The proper go version is referenced. Additional info:
Can't verify this on function level, and I suppose this issue could be fix easily and risk is very low. so close it.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581