Update ODF releases

[ezio-auditore]

Summary by CodeRabbit

This PR updates the OpenShift Data Foundation (ODF) release versions in the Jira lifecycle plugin configuration.

Practical Impact:
The Jira lifecycle plugin manages automated bug triage and lifecycle workflows for the red-hat-storage project in Jira. This change updates the target ODF versions that bugs should be assigned to during validation and merge workflows:

• release-4.21 branch: Bumps target version from odf-4.21.5 to odf-4.21.6
• release-4.21-compatibility branch: Bumps target version from odf-4.21.5 to odf-4.21.6

Both branches retain validate_by_default: true, meaning bugs will continue to be automatically validated against these newer target versions. This ensures that bug tracking and release management for ODF's 4.21 release line remain synchronized with the latest patch version.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@ezio-auditore: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[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: eae384a3-7357-4b8d-9d71-00df5c4ab8f8

📥 Commits

Reviewing files that changed from the base of the PR and between 3b6ff15 and b3076ca.

📒 Files selected for processing (1)

• core-services/jira-lifecycle-plugin/config.yaml

---

Walkthrough

Jira lifecycle plugin configuration is updated to bump the target ODF versions for release-4.21 branches from odf-4.21.5 to odf-4.21.6 across two branch entries.

Changes

ODF Release Version Update

Layer / File(s)	Summary
Target version bump for release-4.21 branches core-services/jira-lifecycle-plugin/config.yaml	Updated target_version for release-4.21 and release-4.21-compatibility entries from odf-4.21.5 to odf-4.21.6.

---

🎯 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 'Update ODF releases' accurately reflects the main change: bumping ODF release versions from odf-4.21.5 to odf-4.21.6 in the configuration file.
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	PR only modifies config.yaml; no Ginkgo test files or test code changes detected. Check is not applicable to configuration-only changes.
Test Structure And Quality	✅ Passed	PR contains standard Go testing.T tests, not Ginkgo tests. Custom check for Ginkgo test code quality is not applicable to this PR.
Microshift Test Compatibility	✅ Passed	PR only modifies a configuration YAML file (jira-lifecycle-plugin/config.yaml) with no Ginkgo e2e tests added. MicroShift compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only updates version numbers in a YAML configuration file (odf-4.21.5 → odf-4.21.6). No Ginkgo e2e tests or test code are added, so SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only JIRA configuration, bumping ODF version references. No deployment manifests, operator code, controllers, or scheduling constraints introduced.
Ote Binary Stdout Contract	✅ Passed	PR only modifies YAML configuration file with no Go code changes; OTE stdout contract check is inapplicable to configuration-only changes.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only modifies config.yaml with version number updates; no new Ginkgo e2e tests added, so check is not applicable.

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ezio-auditore
Once this PR has been reviewed and has the lgtm label, please assign bradmwilliams 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:

• core-services/jira-lifecycle-plugin/OWNERS

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