Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@haircommander
Copy link
Member

@haircommander haircommander commented Dec 22, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

Summary by CodeRabbit

  • Chores

    • Bumped CRI-O to v1.35
    • Updated Kubernetes test version to v1.35
    • Updated default Kubernetes version used by provisioning and test scripts to v1.35
  • Documentation

    • Updated README examples and commands to reference v1.35 (including static bundle examples)

✏️ Tip: You can customize this high-level summary in your review settings.

@openshift-ci openshift-ci bot requested review from QiWang19 and klihub December 22, 2025 16:20
@openshift-ci openshift-ci bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Dec 22, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 22, 2025
@coderabbitai
Copy link

coderabbitai bot commented Dec 22, 2025

Walkthrough

This pull request updates Kubernetes-related version references from v1.34 to v1.35 across dependency metadata, documentation, and test provisioning scripts. No logic or structural configuration changes were introduced.

Changes

Cohort / File(s) Change Summary
Dependency manifest
dependencies.yaml
Updated CRI-O from v1.34 β†’ v1.35 and Kubernetes test version from v1.34 β†’ v1.35.
Documentation
README.md
Bumped displayed example/tag values from v1.34 β†’ v1.35 in two code blocks and a static-bundle example.
Test provisioning (deb)
test/deb/lima.yaml
Updated Kubernetes apt key/repo references and package version variables from v1.34 β†’ v1.35.
Test provisioning (rpm)
test/rpm/lima.yaml
Updated RPM repository/base URLs and interpolated version values from v1.34 β†’ v1.35.
Test scripts
test/scripts/versions.sh
Changed default KUBERNETES_VERSION value from v1.34 β†’ v1.35.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Homogeneous version bumps across multiple files; review primarily for consistent version strings and no accidental changes.
  • Pay extra attention to:
    • test/deb/lima.yaml and test/rpm/lima.yaml (package/repo URL interpolation).
    • Any README examples that must exactly match release tags (typos).

Suggested labels

kind/dependency-change, lgtm

Suggested reviewers

  • QiWang19

Poem

🐰 A hop, a bump, a versions-prance,
From thirty-four to thirty-five I dance.
CRI‑O, kube, in tidy rows,
Tests and docs where fresh wind blows.
Celebrate the updateβ€”carrot toast! πŸ₯•

Pre-merge checks and finishing touches

βœ… Passed checks (3 passed)
Check name Status Explanation
Description Check βœ… Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check βœ… Passed The title 'bump to kube and cri-o 1.35' clearly and concisely summarizes the main change: updating Kubernetes and CRI-O dependencies from v1.34 to v1.35. This directly matches the changeset across all modified files.
Docstring Coverage βœ… Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • πŸ“ Generate docstrings
πŸ§ͺ Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

@bitoku
Copy link
Contributor

bitoku commented Dec 22, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 22, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

πŸ“œ Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 0fa6262 and 84d3699.

πŸ“’ Files selected for processing (5)
  • README.md
  • dependencies.yaml
  • test/deb/lima.yaml
  • test/rpm/lima.yaml
  • test/scripts/versions.sh
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (13)
  • GitHub Check: test / rpm / fedora:42 / s390x
  • GitHub Check: test / deb / debian:13 / arm64
  • GitHub Check: test / deb / ubuntu:24.04 / arm64
  • GitHub Check: test / deb / debian:13 / ppc64le
  • GitHub Check: test / deb / ubuntu:24.04 / s390x
  • GitHub Check: test / deb / debian:13 / s390x
  • GitHub Check: test / rpm / fedora:42 / arm64
  • GitHub Check: test / deb / ubuntu:24.04 / ppc64le
  • GitHub Check: test / rpm / almalinux:10 / arm64
  • GitHub Check: test / rpm / almalinux:10 / ppc64le
  • GitHub Check: test / rpm / fedora:42 / ppc64le
  • GitHub Check: test / deb / kubernetes / amd64
  • GitHub Check: test / rpm / kubernetes / amd64
πŸ”‡ Additional comments (6)
test/rpm/lima.yaml (1)

27-27: LGTM!

The Kubernetes version update for RPM-based provisioning is consistent with the version bump across the repository.

test/deb/lima.yaml (1)

25-25: LGTM!

The Kubernetes version update for Debian-based provisioning is consistent with the version bump across the repository.

test/scripts/versions.sh (1)

6-6: LGTM!

The default Kubernetes version update is consistent with the version bump across the repository.

README.md (1)

157-159: LGTM!

The version variable definitions are updated consistently for both Kubernetes and CRI-O to v1.35.

dependencies.yaml (2)

18-18: Version bump is approved.

Kubernetes v1.35.0 was released on December 17, 2025 and includes 17 enhancements graduated to stable status. The version update is appropriate and aligns with the latest production-ready release.


4-4: Version bump to v1.35 is correct and verified.

CRI-O v1.35.0 has been released and stable v1.35.z packages are available. The update aligns with the PR objective and current available releases.


```shell
curl https://raw.githubusercontent.com/cri-o/packaging/main/get | bash -s -- -t v1.34.0
curl https://raw.githubusercontent.com/cri-o/packaging/main/get | bash -s -- -t v1.35.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

gh api repos/cri-o/cri-o/git/ref/tags/v1.35.0 --jq '.ref' 2>&1 || echo "Tag v1.35.0 not found"

Repository: cri-o/packaging

Length of output: 219


🏁 Script executed:

gh api repos/cri-o/cri-o/git/refs/tags --jq '.[] | select(.ref | contains("v1.35")) | .ref' 2>&1 | head -20

Repository: cri-o/packaging

Length of output: 41


🏁 Script executed:

gh api repos/cri-o/cri-o/git/refs/tags --jq '.[] | .ref' 2>&1 | head -20

Repository: cri-o/packaging

Length of output: 420


🏁 Script executed:

gh api repos/cri-o/cri-o/git/refs/tags --jq '.[-20:] | .[] | .ref' 2>&1

Repository: cri-o/packaging

Length of output: 419


Update the example to use an existing tag or clarify the v1.35 release timeline.

The tag v1.35.0 does not currently exist in the cri-o/cri-o repository. The latest available tags are in the v1.9.x range (v1.9.16 is the most recent). Either update the example to reference an existing tag, or document when the v1.35 release will be available.

πŸ€– Prompt for AI Agents
In README.md around line 337, the example uses a non-existent tag v1.35.0;
update the example to reference an actual existing tag (for example v1.9.16 or
the repository's latest release tag) or change the text to use a clearly
documented placeholder (e.g., "use the desired tag or latest release") and add a
short note pointing readers to the cri-o/cri-o tags/releases page for the
correct tag and release timeline.

@openshift-merge-bot openshift-merge-bot bot merged commit 3c24dac into cri-o:main Dec 22, 2025
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants