chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v1.24.6-1756993846

[red-hat-konflux]

This PR contains the following updates:

Package	Update	Change
registry.access.redhat.com/ubi9/go-toolset	patch	1.24.4-1752083840 -> 1.24.6-1756993846
registry.access.redhat.com/ubi9/go-toolset	minor	1.21.9-1.1714671022 -> 1.24.6-1756993846
registry.access.redhat.com/ubi9/go-toolset	minor	1.20.12-3.1713832665 -> 1.24.6-1756993846
registry.access.redhat.com/ubi9/go-toolset	minor	1.19.13-4.1697647145 -> 1.24.6-1756993846

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Configuration

📅 Schedule: Branch creation - At 07:00 PM through 11:59 PM and 12:00 AM through 02:59 AM, every 2 days and , on day 4 of the month, and on Thursday ( * 19-23,0-2 */2,4 * 4 ) in timezone America/Toronto, 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 these updates again.

---

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

---

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a devfile 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-sigs/prow repository.

[thepetk]

/lgtm

I have updated the branch and removed the updates from older go stacks.

Created a PR to deprecate the old ones and exclude them from the renovate updates (as the runner tends to bump them to 1.24)

@michael-valdron as there are commits of mine in the PR too I'll let you merge once ready

[thepetk]

/ok-to-test

[red-hat-konflux]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[RomanNikitenko]

I tested simple actions for the go-1.4.0, like:

• open a file
• create a terminal
• run a task
• run a command
• install an extension

I didn't detect any problem with the new image tag.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: red-hat-konflux[bot], RomanNikitenko, thepetk

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 [thepetk]

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

[michael-valdron]

/retest

[openshift-ci]

@red-hat-konflux[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v4.16-registry-test	ed61a83	link	true	/test v4.16-registry-test

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.