OCPBUGS-52945: Update Go version in go.mod to 1.22.0

[danielmellado]

This commit modifies the go.mod file to explicitly use go version
1.22.0. This is done in order to avoid konflux build issues when using
hermetic builds related to failure finding the toolchain.

• I added CHANGELOG entry for this change.
• Change is not relevant to the end user.

[jan--f]

A toolchain directive might be better here. This will be required in future versions anyway iiuc and might be upstreamable. See golang/go#62278 (comment)

@saswatamcode wdyt?

[jan--f]

We can merge this to unblock the konflux build but we'll need the bug chain to get this merged.
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danielmellado, jan--f

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 [danielmellado,jan--f]

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

[openshift-ci]

@danielmellado: all tests passed!

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.

[danielmellado]

We can merge this to unblock the konflux build but we'll need the bug chain to get this merged. /lgtm

I was hoping to only have this in 4.18 and have the Konflux tooling patch this on the fly, had a few conversation but not sure about the timing, Will create a OCPBUGS and make this the backport, thanks!

[openshift-ci-robot]

@danielmellado: This pull request references Jira Issue OCPBUGS-52945, which is invalid:

• expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.19" instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-52945 to depend on a bug targeting a version in 4.19.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This commit modifies the go.mod file to explicitly use go version
1.22.0. This is done in order to avoid konflux build issues when using
hermetic builds related to failure finding the toolchain.

• I added CHANGELOG entry for this change.
• Change is not relevant to the end user.

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 openshift-eng/jira-lifecycle-plugin repository.

[danielmellado]

/jira refresh

[openshift-ci-robot]

@danielmellado: This pull request references Jira Issue OCPBUGS-52945, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-52945 to depend on a bug targeting a version in 4.19.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[danielmellado]

/jira refresh

[openshift-ci-robot]

@danielmellado: This pull request references Jira Issue OCPBUGS-52945, which is invalid:

• expected Jira Issue OCPBUGS-52945 to depend on a bug targeting a version in 4.19.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[danielmellado]

/jira refresh

[danielmellado]

/jira refresh

[danielmellado]

/jira refresh

[danielmellado]

/jira refresh

[openshift-ci-robot]

@danielmellado: This pull request references Jira Issue OCPBUGS-52945, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-52962 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-52962 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
• bug has dependents

Requesting review from QA contact:
/cc @juzhao

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[Tai-RedHat]

/label cherry-pick-approved

[jan--f]

/label backport-risk-assessed

[openshift-ci-robot]

@danielmellado: Jira Issue OCPBUGS-52945: All pull requests linked via external trackers have merged:

• openshift/thanos#159

Jira Issue OCPBUGS-52945 has been moved to the MODIFIED state.

In response to this:

This commit modifies the go.mod file to explicitly use go version
1.22.0. This is done in order to avoid konflux build issues when using
hermetic builds related to failure finding the toolchain.

• I added CHANGELOG entry for this change.
• Change is not relevant to the end user.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: thanos
This PR has been included in build ose-thanos-container-v4.18.0-202503131105.p0.gf1599f6.assembly.stream.el9.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.18.0-0.nightly-2025-04-01-173525