USHIFT-7487: Bump CRI-O dependency to 5.1.0 for release-5.1 - #7249
USHIFT-7487: Bump CRI-O dependency to 5.1.0 for release-5.1#7249eslutsky wants to merge 2 commits into
Conversation
Update the CRI-O version requirement in the RPM spec to match the OCP 5.1 dependency repository (cri-o-5.1.0). cri-tools remains at 1.36.0 as that is the version shipped in the 5.1-el9-beta repo. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe changes align MicroShift release metadata with OpenShift 5.1 and update the RPM CRI-O dependency to the 5.1.x version range. ChangesRelease alignment
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized dependency version update presents no actionable merge-blocking risk at the current head; it is merge-ready after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (1 skipped: 1 unsupported.) Full details: Stable And Deterministic Test NamesExplanation PASS: The complete pull-request range changes only Full details: Test Structure And QualityExplanation PASS: The pull request changes only Full details: Microshift Test CompatibilityExplanation PASS: The pull request changes only Full details: Single Node Openshift (Sno) Test CompatibilityExplanation PASS — The pull request changes only the RPM spec and Full details: Topology-Aware Scheduling CompatibilityExplanation PASS: The check is not applicable. The verified diff changes only RPM dependency metadata, release-version test variables, and an unrelated GitHub utility constant. No deployment manifest, operator, or controller code changes were made, and no scheduling fields appear in the added or removed lines. Full details: Ote Binary Stdout ContractExplanation PASS: The PR changes only Full details: Ipv6 And Disconnected Network Test CompatibilityExplanation PASS: The pull request adds no Ginkgo e2e tests. The diff contains only Full details: No-Weak-CryptoExplanation PASS: The pull request changes only RPM version constraints and release-version metadata. The committed diff contains no MD5, SHA1, DES, 3DES, RC4, Blowfish, ECB, custom cryptography, or secret/token comparisons. The Full details: Container-PrivilegesExplanation The pull request changes only Full details: No-Sensitive-Data-In-LogsExplanation PASS: The pull request changes only an RPM dependency constraint and release/version repository variables. The exact diffs add no logging statements or sensitive values. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@eslutsky: This pull request references USHIFT-7487 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.1.0" version, but no target version was set. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
|
/override ci/prow/e2e-aws-tests |
|
@eslutsky: Overrode contexts on behalf of eslutsky: ci/prow/e2e-aws-tests, ci/prow/e2e-aws-tests-arm, ci/prow/e2e-aws-tests-bootc-arm-el10, ci/prow/e2e-aws-tests-bootc-arm-el9, ci/prow/e2e-aws-tests-bootc-el10, ci/prow/e2e-aws-tests-bootc-el9 DetailsIn response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eslutsky, pacevedom The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/verified by CI |
|
@eslutsky: This PR has been marked as verified by DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
New changes are detected. LGTM label has been removed. |
|
@eslutsky: This pull request references USHIFT-7487 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.1.0" version, but no target version was set. Retaining the jira/valid-bug label as it was manually added. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
Run generate_common_versions.py 5.1 to update version variables after the 5.0 -> 5.1 OCP_VERSION bump. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
0bcbf28 to
c85b782
Compare
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
@eslutsky: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Summary
>= 1.36.0, < 1.37.0to>= 5.1.0, < 5.2.0in the RPM spec to match the OCP 5.1 dependency repocri-toolsstays at1.36.0as that is the version shipped in the 5.1-el9-beta repoTest plan
🤖 Generated with Claude Code
Summary by CodeRabbit
Bug Fixes
Chores