Update version to 6.2.13

[xperimental]

/cc @jcantrill
/assign @xperimental

Links

• JIRA: LOG-9687

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 459d446b-4fe8-46ef-835a-313ad2dcd9c9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[qodo-for-rh-openshift]

PR Summary by Qodo

Bump Cluster Logging operator version metadata to 6.2.13

⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Update container image label version to 6.2.13.
• Bump OLM bundle templating values (skipRange, version, CSV name) to 6.2.13.
• Point the stable-6.2 channel to the 6.2.13 currentCSV.

Diagram

graph TD
  A["Release 6.2.13"] --> B["Dockerfile.art"] --> C["Image label version"]
  A --> D["bundle/art.yaml"] --> E["CSV templating"]
  A --> F["bundle/cluster-logging-operator.package.yaml"] --> G["Channel currentCSV"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Single source-of-truth version file

• ➕ Reduces risk of inconsistent bumps across Dockerfile/bundle/package metadata
• ➕ Enables validation (CI) to ensure all derived fields match the declared version
• ➖ Requires small build/release pipeline change to read and apply the version
• ➖ May be overkill if bumps are infrequent and already automated elsewhere

2. Automate version bump via script/Make target

• ➕ Keeps current file layout while making bumps repeatable and less error-prone
• ➕ Can enforce updating all required fields (skipRange/name/currentCSV) together
• ➖ Adds another maintenance surface (script)
• ➖ Still relies on correct script usage in the release process

Recommendation: The PR’s direct, explicit bump is appropriate for a patch release and keeps the change low-risk. If version bumps are frequent or have caused mismatches historically, consider introducing a single source-of-truth version (or a bump script) plus a CI check to ensure all version strings (including currentCSV naming) remain consistent.

Files changed (3) +5 / -5

Other (3) +5 / -5

Dockerfile.artBump image label version to 6.2.13 +1/-1

Bump image label version to 6.2.13

• Updates the container label field 'version' from 6.2.12 to 6.2.13 to reflect the new release.

Dockerfile.art

art.yamlUpdate bundle replacement rules for 6.2.13 +3/-3

Update bundle replacement rules for 6.2.13

• Adjusts ART replacement values so 'olm.skipRange', 'version', and CSV 'name' replacements target 6.2.13. This keeps generated bundle/CSV metadata aligned with the release version.

bundle/art.yaml

cluster-logging-operator.package.yamlPoint stable-6.2 channel currentCSV at 6.2.13 +1/-1

Point stable-6.2 channel currentCSV at 6.2.13

• Updates the package channel head so 'currentCSV' references the 6.2.13 CSV. This ensures OLM installs/updates track the intended bundle version.

bundle/cluster-logging-operator.package.yaml

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xperimental

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 [xperimental]

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

[qodo-for-rh-openshift]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

⚠️ Tickets: not configured — ticket URL found in PR but could not be fetched — check ticket provider credentials

✅ Compliance rules (platform): 9 rules

1. Version label mismatch 🐞 Bug ≡ Correctness

Description

Dockerfile.art updates the image LABEL version to 6.2.13, but the built operator will still report
version.Version as 6.2.0 because make build does not regenerate version/version.go. As a
result, startup logs, common Kubernetes labels, and telemetry will continue to reflect 6.2.0 while
the image metadata advertises 6.2.13.

Code

Dockerfile.art[62]

+        version="6.2.13"

Relevance

●●● Strong

Past version-bump PRs updated Dockerfile.art AND version/version.go together; mismatch likely
treated as release-blocking.

PR-#3225
PR-#3347

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The Dockerfile.art build step runs make build (which does not regenerate version/version.go),
while the repo’s current version/version.go is still 6.2.0. The operator uses version.Version
in startup logs and applies it as a common label, so the runtime-reported version will not match the
updated container label.

Dockerfile.art[1-12]
Dockerfile.art[47-62]
Makefile[89-95]
Makefile[170-180]
version/version.go[1-3]
cmd/main.go[91-100]
internal/runtime/runtime.go[114-123]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`Dockerfile.art` bumps the container label to `6.2.13`, but the operator’s embedded version (`version.Version`) stays at `6.2.0` under this Dockerfile because it runs `make build` only.

### Issue Context
- `make build` does **not** run the `generate` target that writes `version/version.go` from `CI_CONTAINER_VERSION`/`VERSION`.
- The current checked-in `version/version.go` is `6.2.0`, and this value is used in logs and common labels.

### Fix
Pick one of the following (prefer an approach that guarantees the Docker label and embedded version are derived from the same single source of truth):
1) **Update `version/version.go` in this PR** to `6.2.13` so the binary reports the same version as the label.
2) **Teach `Dockerfile.art` to set the embedded version during build** (e.g., write `version/version.go` from a build ARG like `CI_CONTAINER_VERSION` before `make build`, or run the minimal step that updates just this file).

### Fix Focus Areas
- Dockerfile.art[1-12]
- Dockerfile.art[47-62]
- Makefile[89-95]
- Makefile[170-180]
- version/version.go[1-3]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

[qodo-for-rh-openshift]

1. Version label mismatch 🐞 Bug ≡ Correctness

Dockerfile.art updates the image LABEL version to 6.2.13, but the built operator will still report
version.Version as 6.2.0 because make build does not regenerate version/version.go. As a
result, startup logs, common Kubernetes labels, and telemetry will continue to reflect 6.2.0 while
the image metadata advertises 6.2.13.

Agent Prompt

### Issue description
`Dockerfile.art` bumps the container label to `6.2.13`, but the operator’s embedded version (`version.Version`) stays at `6.2.0` under this Dockerfile because it runs `make build` only.

### Issue Context
- `make build` does **not** run the `generate` target that writes `version/version.go` from `CI_CONTAINER_VERSION`/`VERSION`.
- The current checked-in `version/version.go` is `6.2.0`, and this value is used in logs and common labels.

### Fix
Pick one of the following (prefer an approach that guarantees the Docker label and embedded version are derived from the same single source of truth):
1) **Update `version/version.go` in this PR** to `6.2.13` so the binary reports the same version as the label.
2) **Teach `Dockerfile.art` to set the embedded version during build** (e.g., write `version/version.go` from a build ARG like `CI_CONTAINER_VERSION` before `make build`, or run the minimal step that updates just this file).

### Fix Focus Areas
- Dockerfile.art[1-12]
- Dockerfile.art[47-62]
- Makefile[89-95]
- Makefile[170-180]
- version/version.go[1-3]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[vparfonov]

/retest-required

[xperimental]

/retest-required

[vparfonov]

/retest-required

[vparfonov]

/test images

[qodo-for-rh-openshift]

Unsupported PR languages

[openshift-ci]

@xperimental: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/functional-target	aa38762	link	true	/test functional-target
ci/prow/images	aa38762	link	true	/test images
ci/prow/e2e-target	aa38762	link	true	/test e2e-target

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.