chore(deps): bump go version to v1.26.5

[rohanKanojia]

Summary

• Bump Go toolchain from 1.26.4 to 1.26.5 in go.mod, CI workflows, and OCI Dockerfile
• Update UBI9 go-toolset builder images to 1.26.5-1783931515 with digest sha256:d8698410eb806fedd5c0ddbd08e981436051e0ed2113b8e402736e7ee578f6f4 in build/Dockerfile and project-clone/Dockerfile

Test plan

• CI passes (unit tests, lint, code coverage)
• Container images build successfully with updated go-toolset image

Made with Cursor

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rohanKanojia
Once this PR has been reviewed and has the lgtm label, please assign dkwon17 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

Warning

Review limit reached

@rohanKanojia, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b9ad879c-26b3-4240-9ea2-7faa8c16b279

📥 Commits

Reviewing files that changed from the base of the PR and between 8501cef and ae8763b.

📒 Files selected for processing (7)

• .ci/oci.Dockerfile
• .github/workflows/code-coverage.yml
• .github/workflows/pr.yml
• .github/workflows/release.yml
• build/Dockerfile
• go.mod
• project-clone/Dockerfile

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[tolusha]

Hi! I'm che-ai-assistant — I help with your pull requests.

Available commands:

• /che-ai-assistant generate-che-doc — Generate a documentation PR based on this PR's changes
• /che-ai-assistant ok-pr-review — Run a comprehensive PR review (summary, code review, deep review, impact analysis)
• /che-ai-assistant ok-pr-readiness — Ensure PR has validation steps
• /che-ai-assistant check-pr-test-failures — Analyze failing CI checks, identify root causes, and suggest fixes
• /che-ai-assistant update-che-e2e-tests — Update Eclipse Che e2e tests
• /che-ai-assistant help — Show this help message

[tolusha]

/che-ai-assistant ok-pr-readiness

Task completed.

[tolusha]

PR Readiness Assessment: PR #1671 — chore(deps): bump go version to v1.26.5

Repository: devfile/devworkspace-operator
Linked Issue: None found

---

#	Criterion	Verdict	Notes
1	Problem Statement	PASS	Dependency update - maintaining current Go toolchain with security/bug fixes from upstream
2	Reproduction Steps	PASS	Not applicable for toolchain version bump - no bug to reproduce
3	Expected Behavior After Fix	PASS	CI and builds should continue working with newer Go version
4	Scope of Changes	PASS	Mechanical version bump across go.mod, CI workflows, and Dockerfiles - all changes are consistent and expected
5	Test Evidence	PASS	Test plan explicitly lists CI checks and container image builds as verification
6	Deployment & Verification Notes	WARN	Partial - test plan covers CI but lacks guidance on verifying the deployed operator itself uses the new Go version

Overall: READY

---

Missing Information

• Add a note about how to verify the deployed operator container was built with Go 1.26.5 (e.g., `go version` check within the running container, or image inspection commands)
• Consider mentioning if there are any known fixes or security issues in Go 1.26.5 that motivated this update (helps reviewers understand urgency)

What's Good

• Comprehensive scope: Updated Go version consistently across all locations (go.mod toolchain, all CI workflows, and all Dockerfiles)
• Pinned container images: Updated UBI9 go-toolset images include both version tag and SHA256 digest for security and reproducibility
• Clear test plan: Explicitly lists CI and container build verification steps
• Clean diff: All changes are mechanical version bumps with no logic changes, making review straightforward
• Good commit hygiene: Chore commit type and clear summary make the intent immediately obvious