Update go version to 1.22

[upadhyeammit]

PR Title 💥

Please title this PR with a summary of the change, along with the JIRA card number.

Suggested formats:

1. Fixes/Refs #RHIROS-XXX - Title
2. RHIROS-XXX Title
3. RHINENG-XXX Title

Feel free to remove this section from PR description once done.

Why do we need this change? 💭

Please include the context of this change here. If the change depends on Kruize add details about that as well!

Documentation update? 📝

• Yes
• No

Security Checklist 🔒

Upon raising this PR please go through RedHatInsights/secure-coding-checklist

💂‍♂️ Checklist 🎯

• Does this change depend on specific version of Kruize
  • If yes what is the version no:
  • Is that image available in production or needs deployment?
• Bugfix
• New Feature
• Refactor
• Unittests Added
• DRY code
• Dependency Added
• DB Migration Added

Additional 📣

Feel free to add any other relevant details such as links, notes, screenshots, here.

[upadhyeammit]

I am not linking the RHINENG-5181 to the pull request as the bugzilla attached to this ticket is not yet resolved with the Errata.
At the same time, if I see the go releases then only recent two releases are supported. That does mean 1.23 and 1.22 however the ubi8/go-toolset is only having 1.21.13 as the latest tag which was released 23 days back. Looking at this, mostly we need to find other way to compile to go code as it seems go-toolset is lagging a lot!

[saltgen]

@upadhyeammit Shall we look around for some other image? I would like to check if there is a possibility to go for 1.22 or 1.23 atm.
Additionally, looks like the PR check is failing.

[saltgen]

/retest

[saltgen]

@upadhyeammit I think it is better to avoid the minor version here, since we don't seem to have that granularity in the Dockerfile tag, thoughts?

[upadhyeammit]

yeah.. actually its kind of like if we run the go mod tidy then it adds the minor version, updated it

[saltgen]

@upadhyeammit Let's update the version here as well.

[upadhyeammit]

@upadhyeammit Let's update the version here as well.

added already

[upadhyeammit]

Its weird, if we remove the minor version then linting fails,

$ make lint
/home/amit/work/insights/ros/ros-ocp-backend/bin/golangci-lint run --timeout=3m ./...
ERRO Running error: context loading failed: no go files to analyze: running `go mod tidy` may solve the problem 
make: *** [Makefile:79: lint] Error 5
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ git status
On branch update-go-packages
nothing to commit, working tree clean
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ go mod tidy
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ git status
On branch update-go-packages
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   go.mod

no changes added to commit (use "git add" and/or "git commit -a")
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ make lint
/home/amit/work/insights/ros/ros-ocp-backend/bin/golangci-lint run --timeout=3m ./...
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ git diff
diff --git a/go.mod b/go.mod
index c2959f6..a5fb282 100644
--- a/go.mod
+++ b/go.mod
@@ -1,6 +1,6 @@
 module github.com/redhatinsights/ros-ocp-backend
 
-go 1.22
+go 1.22.0

[upadhyeammit]

Its weird, if we remove the minor version then linting fails,

$ make lint
/home/amit/work/insights/ros/ros-ocp-backend/bin/golangci-lint run --timeout=3m ./...
ERRO Running error: context loading failed: no go files to analyze: running `go mod tidy` may solve the problem 
make: *** [Makefile:79: lint] Error 5
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ git status
On branch update-go-packages
nothing to commit, working tree clean
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ go mod tidy
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ git status
On branch update-go-packages
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   go.mod

no changes added to commit (use "git add" and/or "git commit -a")
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ make lint
/home/amit/work/insights/ros/ros-ocp-backend/bin/golangci-lint run --timeout=3m ./...
amit@fedora ~/work/insights/ros/ros-ocp-backend (update-go-packages)$ git diff
diff --git a/go.mod b/go.mod
index c2959f6..a5fb282 100644
--- a/go.mod
+++ b/go.mod
@@ -1,6 +1,6 @@
 module github.com/redhatinsights/ros-ocp-backend
 
-go 1.22
+go 1.22.0

as its failing https://github.com/RedHatInsights/ros-ocp-backend/actions/runs/11835786586/job/32979299087?pr=267 . I am repushing with minor version

[saltgen]

@upadhyeammit I see that the image has 1.22.7 so we could do something like this and go mod tidy does not modify this further.

go 1.22.7

toolchain go1.22.7

I also noticed, that the minor versions don't change in the images by looking the previous tags.
This also means we should probably have a look if the e2e runs as expected, locally.

[upadhyeammit]

@upadhyeammit I see that the image has 1.22.7 so we could do something like this and go mod tidy does not modify this further.

go 1.22.7

toolchain go1.22.7

I also noticed, that the minor versions don't change in the images by looking the previous tags. This also means we should probably have a look if the e2e runs as expected, locally.

I tried it and now I can see go mod tidy just kept one entry,

$ git diff
diff --git a/go.mod b/go.mod
index 1f4cc93..95c1fbc 100644
--- a/go.mod
+++ b/go.mod
@@ -1,8 +1,6 @@
 module github.com/redhatinsights/ros-ocp-backend
 
-go 1.22.0
-
-toolchain go1.22.9
+go 1.22.7

[upadhyeammit]

/retest

[saltgen]

@upadhyeammit Thanks for the changes 👍🏼