🌱 chore: upgrade to go 1.26

[tesshuflower]

Upgrades Go version from 1.25 to 1.26.

Changes:

• go.mod — go directive updated to 1.26.0
• .github/workflows/go-presubmit.yml — GO_VERSION updated to 1.26
• .github/workflows/go-postsubmit.yml — GO_VERSION updated to 1.26
• .github/workflows/go-release.yml — GO_VERSION updated to 1.26
• .github/workflows/cloudevents-integration.yml — GO_VERSION updated to 1.26 (was incorrectly pinned to 1.24)
• build/Dockerfile.example — base image updated to golang:1.26-bookworm

Relates to: open-cluster-management-io/ocm#1555

Summary by CodeRabbit

• Chores
  • Updated Go toolchain version to 1.26 across build configurations and CI/CD workflows.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 42307cf6-7c1f-4fee-9d0e-3dbe735726f5

📥 Commits

Reviewing files that changed from the base of the PR and between 5017f37 and 6991cde.

📒 Files selected for processing (6)

• .github/workflows/cloudevents-integration.yml
• .github/workflows/go-postsubmit.yml
• .github/workflows/go-presubmit.yml
• .github/workflows/go-release.yml
• build/Dockerfile.example
• go.mod

---

Walkthrough

Go toolchain version updated to 1.26 across the project: module definition in go.mod, container builder image in build/Dockerfile.example, and all four GitHub Actions workflows that define GO_VERSION for CI/CD jobs.

Changes

Go Toolchain Upgrade

Layer / File(s)	Summary
Go toolchain upgrade to 1.26 go.mod, build/Dockerfile.example, .github/workflows/cloudevents-integration.yml, .github/workflows/go-postsubmit.yml, .github/workflows/go-presubmit.yml, .github/workflows/go-release.yml	Go version directive in go.mod updated to 1.26.0, Docker builder image updated to golang:1.26-bookworm, and GO_VERSION environment variable updated across all GitHub Actions workflows.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly Related PRs

• open-cluster-management-io/addon-framework#320: Both PRs directly adjust the Go toolchain version in go.mod and the GitHub Actions GO_VERSION env for the same workflow files (plus builder image Go base in build/Dockerfile.example), so the changes overlap at the version-setting code level.

Suggested Labels

ok-to-test

Suggested Reviewers

• zhujian7
• qiujian16

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: upgrading Go from version 1.25 to 1.26 across multiple workflow files and configuration files.
Description check	✅ Passed	The description provides a clear summary and comprehensive list of all changed files with specific details about what was updated. While it doesn't follow the exact template structure with distinct 'Summary' and 'Related issue(s)' sections, the content is well-organized and complete.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 and usage tips.}

[tesshuflower]

@qiujian16 or @jnpacker could I get a review on this one?

[qiujian16]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhaiducek, qiujian16, tesshuflower

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [qiujian16]

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