OCPBUGS-97995: Start using openshift-v5 mirror dependencies

[ggiguash]

Summary by CodeRabbit

• Bug Fixes
  • Updated package requirements to use newer supported versions of cri-o and cri-tools, improving alignment with the current release stream.
  • Adjusted the beta dependencies source to point to the latest repository location, helping ensure builds and tests pull the correct packages.

[openshift-ci-robot]

@ggiguash: This pull request references Jira Issue OCPBUGS-97995, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

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

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

Walkthrough

Updates RPM Requires version constraints for cri-o and cri-tools from >= 1.34.0, < 1.36.0 to >= 1.36.0, < 1.37.0, removing an accompanying comment. Also updates the RHOCP_MINOR_Y_BETA mirror URL from openshift-v4/4.22-el9-beta to openshift-v5/5.0-el9-beta.

Changes

Version Bump Updates

Layer / File(s)	Summary
Dependency and mirror version bumps packaging/rpm/microshift.spec, test/bin/common_versions.sh	Bumps cri-o/cri-tools RPM version requirements and updates the beta dependencies mirror URL to the next release version.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested labels: ready-for-human-review

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash

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

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

[openshift-ci-robot]

@ggiguash: This pull request references Jira Issue OCPBUGS-97995, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

Summary by CodeRabbit

• Bug Fixes
• Updated package requirements to use newer supported versions of cri-o and cri-tools, improving alignment with the current release stream.
• Adjusted the beta dependencies source to point to the latest repository location, helping ensure builds and tests pull the correct packages.

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.

[openshift-ci]

@ggiguash: 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/e2e-aws-tests-bootc-periodic-arm-el10	e344abb	link	true	/test e2e-aws-tests-bootc-periodic-arm-el10
ci/prow/e2e-aws-tests-bootc-periodic-el10	e344abb	link	true	/test e2e-aws-tests-bootc-periodic-el10

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.