Update Go builder from 1.24 to 1.25 for cluster-logging-operator release 6.5

[vparfonov]

Update Go builder from 1.24 to 1.25 for cluster-logging-operator release 6.5

releted to:

• LOG-9379: Fix CVE-2026-33813 in golang.org/x/image cluster-logging-operator#3266
• https://redhat.atlassian.net/browse/LOG-9379

Summary by CodeRabbit

• Chores
  • Updated CI build environment to use Go 1.25 instead of Go 1.24.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 58f654ae-6783-4608-be47-28f1c9e4a1dd

📥 Commits

Reviewing files that changed from the base of the PR and between 15721e7 and f59ea40.

📒 Files selected for processing (1)

• ci-operator/config/openshift/cluster-logging-operator/openshift-cluster-logging-operator-release-6.5.yaml

---

Walkthrough

Update CI builder image version in cluster-logging-operator release 6.5 configuration, bumping Go builder and build root image tags from 1.24 to 1.25 OpenShift variant.

Changes

CI Builder Image Update

Layer / File(s)	Summary
Configuration Update ci-operator/config/openshift/cluster-logging-operator/openshift-cluster-logging-operator-release-6.5.yaml	base_images.go_builder.tag and build_root.image_stream_tag.tag are both bumped from rhel-9-golang-1.24-openshift-4.21 to rhel-9-golang-1.25-openshift-4.21.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically describes the main change: updating the Go builder version from 1.24 to 1.25 for the cluster-logging-operator release 6.5, which matches the actual YAML configuration update in the changeset.
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.
Stable And Deterministic Test Names	✅ Passed	The pull request only modifies a YAML CI configuration file updating Go builder versions. No test code or test files are included, making the Ginkgo test naming check inapplicable.
Test Structure And Quality	✅ Passed	This pull request modifies only a CI operator configuration YAML file, updating Go builder image versions from 1.24 to 1.25. The custom check assesses Ginkgo test code quality, but this PR does not introduce or modify any test files or Ginkgo test code.
Microshift Test Compatibility	✅ Passed	The custom check for MicroShift Test Compatibility is not applicable as this PR only modifies a CI configuration YAML file to update the Go builder image version, with no new Ginkgo e2e tests added or modified.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR modifies only CI/CD configuration files (Go builder image versions in YAML) with no test code changes, so the SNO compatibility check is not applicable and passes by default.
Topology-Aware Scheduling Compatibility	✅ Passed	PR updates only Go builder image version in CI/CD configuration file, not deployment manifests or operator code.
Ote Binary Stdout Contract	✅ Passed	Pull request contains only CI configuration YAML changes with no Go source code modifications, making the OTE Binary Stdout Contract check inapplicable.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only CI operator config file updating Go builder image version; contains no test code or Ginkgo tests.

_{✏️ 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

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@vparfonov: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-cluster-logging-operator-release-6.5-ci-index-cluster-logging-operator-bundle	openshift/cluster-logging-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-release-6.5-e2e-target	openshift/cluster-logging-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-release-6.5-functional-target	openshift/cluster-logging-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-release-6.5-images	openshift/cluster-logging-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-release-6.5-lint	openshift/cluster-logging-operator	presubmit	Ci-operator config changed
pull-ci-openshift-cluster-logging-operator-release-6.5-unit	openshift/cluster-logging-operator	presubmit	Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[vparfonov]

/pj-rehearse pull-ci-openshift-cluster-logging-operator-release-6.5-unit

[openshift-merge-bot]

@vparfonov: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[jcantrill]

possibly duplicates #75406

[vparfonov]

possibly duplicates #75406

no, this is for release 6.5

[jcantrill]

/approve
/lgtm

[jcantrill]

/pj-rehearse ack

[openshift-merge-bot]

@jcantrill: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, vparfonov

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:

• ci-operator/config/openshift/cluster-logging-operator/OWNERS [jcantrill]

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

[openshift-ci]

@vparfonov: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.