DNM, EUS/OADP releases

[weshayutin]

Why the changes were made

How to test the changes made

Summary by CodeRabbit

• Documentation
  • Reformatted existing 4.23 entry and expanded the version mapping to add upcoming versions 5.0, 5.1, and 5.2 with corresponding Velero mappings and updated release timelines through Q3 2027.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

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

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 40b4d49 and a478290.

📒 Files selected for processing (1)

• PARTNERS.md

🚧 Files skipped from review as they are similar to previous changes (1)

• PARTNERS.md

---

Walkthrough

PARTNERS.md updated: reformatted the 4.23 row and added planned version mappings for 5.0, 5.1, and 5.2 with corresponding OADP/Velero versions and updated release timelines through Q3 2027.

Changes

Cohort / File(s)	Summary
Documentation Update PARTNERS.md	Reformatted existing 4.23 table row; added new version mapping rows for 5.0, 5.1, and 5.2 with associated OADP and Velero versions and revised release timeline entries (extends planned releases through Q3 2027).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description contains only empty template placeholders with no substantive content, explanations of why changes were made, or testing instructions provided.	Fill in the 'Why the changes were made' section with context about the new releases, and provide testing guidance in 'How to test' section.
Title check	❓ Inconclusive	The title 'DNM, EUS/OADP releases' refers to a real part of the change (updating release information) but is cryptic and lacks clarity about what is being changed; 'DNM' is unexplained and the title doesn't clearly convey the primary change.	Use a clearer title that explains the change, e.g., 'Update PARTNERS.md with EUS and upcoming OADP release versions' or provide context for abbreviations like DNM.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names	✅ Passed	All test names in this PR are stable and deterministic, using static descriptive strings with no dynamic content like pod names, timestamps, UUIDs, or random identifiers.
Test Structure And Quality	✅ Passed	The custom check for Test Structure and Quality is not applicable as the PR only modifies PARTNERS.md documentation with no test code changes.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

PARTNERS.md (1)

32-43: Consider updating the OADP Plugins table for consistency.

The main version mapping table now includes OpenShift versions 5.0, 5.1, and 5.2, but the OADP Plugins table (lines 32-43) has not been updated with corresponding entries. For documentation completeness and consistency, consider adding plugin version information for these new OpenShift versions, or add a note if this information is not yet available.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@PARTNERS.md` around lines 32 - 43, Update the OADP Plugins table in
PARTNERS.md to include entries for OpenShift 5.0, 5.1, and 5.2 to match the main
version mapping table: add corresponding rows specifying OADP Version, Velero
Version, kubevirt-velero-plugin, hypershift-oadp-plugin (or "n/a" if unknown),
and channel for each new OpenShift version; if plugin versions are not yet
known, add those OpenShift rows with a clear placeholder like "TBD" or a note
column indicating unavailable data to keep the table consistent and complete.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@PARTNERS.md`:
- Line 1: Fix the markdown heading in PARTNERS.md by removing the stray leading
"n" so the line reads "# OADP Partner Information" (update the affected heading
line directly to use proper Markdown heading syntax).

---

Nitpick comments:
In `@PARTNERS.md`:
- Around line 32-43: Update the OADP Plugins table in PARTNERS.md to include
entries for OpenShift 5.0, 5.1, and 5.2 to match the main version mapping table:
add corresponding rows specifying OADP Version, Velero Version,
kubevirt-velero-plugin, hypershift-oadp-plugin (or "n/a" if unknown), and
channel for each new OpenShift version; if plugin versions are not yet known,
add those OpenShift rows with a clear placeholder like "TBD" or a note column
indicating unavailable data to keep the table consistent and complete.

---

ℹ️ Review info

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

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 87b9ef4 and 40b4d49.

📒 Files selected for processing (1)

• PARTNERS.md

[openshift-ci]

@weshayutin: 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kaovilai, weshayutin

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

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