NO-JIRA: sync with upstream 2026-07-23#405
Conversation
Signed-off-by: Calum Murray <cmurray@redhat.com>
|
@openshift-ci-robot: This pull request explicitly references no jira issue. 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. |
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: openshift-ci-robot The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
* cleanup: point eval targets and docs to new eval format Signed-off-by: Calum Murray <cmurray@redhat.com> * cleanup: remove unused old eval suites Signed-off-by: Calum Murray <cmurray@redhat.com> --------- Signed-off-by: Calum Murray <cmurray@redhat.com>
…ners#1327) Follow-up to containers#1325 / containers#1314. containers#1325 removed the top-level evals/claude-code and evals/openai-agent configs but left a few references to the retired agent naming behind. - Delete evals/tasks/kubevirt/{claude-code,openai-agent}/eval.yaml: old-format (type: "builtin.claude-code" / "builtin.llm-agent") under retired agent-named dirs, unreachable via the new agent names, and redundant with evals/core-eval-testing/<agent>/eval-kubevirt.yaml. - Reword the "Eval configs" priority list in evals/README.md so the per-suite override no longer claims kubevirt ships one (none do now) and core-eval-testing is documented as the canonical config. - Point the toolset-design review checklist at evals/core-eval-testing/<agent>/eval-<suite>.yaml instead of the old claude-code / openai-agent names. Signed-off-by: Marc Nuri <marc@marcnuri.com>
Signed-off-by: Calum Murray <cmurray@redhat.com>
Bumps the kubernetes group with 8 updates: | Package | From | To | | --- | --- | --- | | [k8s.io/api](https://github.com/kubernetes/api) | `0.36.2` | `0.36.3` | | [k8s.io/apiextensions-apiserver](https://github.com/kubernetes/apiextensions-apiserver) | `0.36.2` | `0.36.3` | | [k8s.io/apimachinery](https://github.com/kubernetes/apimachinery) | `0.36.2` | `0.36.3` | | [k8s.io/cli-runtime](https://github.com/kubernetes/cli-runtime) | `0.36.2` | `0.36.3` | | [k8s.io/client-go](https://github.com/kubernetes/client-go) | `0.36.2` | `0.36.3` | | [k8s.io/kubectl](https://github.com/kubernetes/kubectl) | `0.36.2` | `0.36.3` | | [k8s.io/metrics](https://github.com/kubernetes/metrics) | `0.36.2` | `0.36.3` | | [k8s.io/streaming](https://github.com/kubernetes/streaming) | `0.36.2` | `0.36.3` | Updates `k8s.io/api` from 0.36.2 to 0.36.3 - [Commits](kubernetes/api@v0.36.2...v0.36.3) Updates `k8s.io/apiextensions-apiserver` from 0.36.2 to 0.36.3 - [Release notes](https://github.com/kubernetes/apiextensions-apiserver/releases) - [Commits](kubernetes/apiextensions-apiserver@v0.36.2...v0.36.3) Updates `k8s.io/apimachinery` from 0.36.2 to 0.36.3 - [Commits](kubernetes/apimachinery@v0.36.2...v0.36.3) Updates `k8s.io/cli-runtime` from 0.36.2 to 0.36.3 - [Commits](kubernetes/cli-runtime@v0.36.2...v0.36.3) Updates `k8s.io/client-go` from 0.36.2 to 0.36.3 - [Changelog](https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md) - [Commits](kubernetes/client-go@v0.36.2...v0.36.3) Updates `k8s.io/kubectl` from 0.36.2 to 0.36.3 - [Commits](kubernetes/kubectl@v0.36.2...v0.36.3) Updates `k8s.io/metrics` from 0.36.2 to 0.36.3 - [Commits](kubernetes/metrics@v0.36.2...v0.36.3) Updates `k8s.io/streaming` from 0.36.2 to 0.36.3 - [Commits](kubernetes/streaming@v0.36.2...v0.36.3) --- updated-dependencies: - dependency-name: k8s.io/api dependency-version: 0.36.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: kubernetes - dependency-name: k8s.io/apiextensions-apiserver dependency-version: 0.36.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: kubernetes - dependency-name: k8s.io/apimachinery dependency-version: 0.36.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: kubernetes - dependency-name: k8s.io/cli-runtime dependency-version: 0.36.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: kubernetes - dependency-name: k8s.io/client-go dependency-version: 0.36.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: kubernetes - dependency-name: k8s.io/kubectl dependency-version: 0.36.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: kubernetes - dependency-name: k8s.io/metrics dependency-version: 0.36.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: kubernetes - dependency-name: k8s.io/streaming dependency-version: 0.36.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: kubernetes ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
daf58ae to
27218d7
Compare
|
@openshift-ci-robot: all tests passed! 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. |
2uasimojo
left a comment
There was a problem hiding this comment.
Is there a reason we wouldn't auto-merge sync PRs with green CI?
|
Overall I'm happy with auto merge once we fix a few issues with the sync (currently it can overwrite the README tools list...) |
🔄 Upstream Sync
Update: Fri Jul 24 08:02:27 UTC 2026
New changes detected from upstream: