Skip to content

chore(deps): update registry.redhat.io/rhel9/rhel-bootc docker tag to v9.7-1777449541#2091

Open
red-hat-konflux[bot] wants to merge 1 commit intodevelfrom
konflux/mintmaker/devel/registry.redhat.io-rhel9-rhel-bootc-9.x
Open

chore(deps): update registry.redhat.io/rhel9/rhel-bootc docker tag to v9.7-1777449541#2091
red-hat-konflux[bot] wants to merge 1 commit intodevelfrom
konflux/mintmaker/devel/registry.redhat.io-rhel9-rhel-bootc-9.x

Conversation

@red-hat-konflux
Copy link
Copy Markdown
Contributor

@red-hat-konflux red-hat-konflux Bot commented May 2, 2026

This PR contains the following updates:

Package Type Update Change
registry.redhat.io/rhel9/rhel-bootc final patch 9.7-17769007699.7-1777449541

Configuration

📅 Schedule: Branch creation - Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

… v9.7-1777449541

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 2, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 80b70c0f-55b8-4cb8-8adc-7ac0580810f9

📥 Commits

Reviewing files that changed from the base of the PR and between 10a4824 and 3d91ae5.

📒 Files selected for processing (1)
  • config/peerpods/podvm/bootc/Containerfile.rhel

Walkthrough

Updated the base container image tag for the podvm-bootc stage in the RHEL bootc Containerfile from digest 9.7-1776900769 to 9.7-1777449541. No build logic, configuration, or arguments were altered.

Changes

Base Image Update

Layer / File(s) Summary
Container Build Configuration
config/peerpods/podvm/bootc/Containerfile.rhel
podvm-bootc stage base image tag updated from registry.redhat.io/rhel9/rhel-bootc:9.7-1776900769 to registry.redhat.io/rhel9/rhel-bootc:9.7-1777449541.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically summarizes the main change: updating a Docker base image tag to a newer version.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed All Ginkgo test names in newly added test files use static, descriptive strings with no dynamic values like timestamps, generated IDs, or runtime-specific information.
Test Structure And Quality ✅ Passed PR modifies only Docker image tag in Containerfile.rhel; no test files modified, so custom test code check does not apply.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests or test code added; PR contains only a single-line Docker base image tag dependency update.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR does not add any new Ginkgo e2e tests. The change is limited to updating a Docker image tag in a Containerfile.
Topology-Aware Scheduling Compatibility ✅ Passed Pull request only updates container image base tag without modifying scheduling constraints or deployment logic.
Ote Binary Stdout Contract ✅ Passed PR contains only a Containerfile base image tag update with no Go source code modifications, making it outside the scope of the OTE Binary Stdout Contract check.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only updates Docker base image tag in Containerfile with no new Ginkgo e2e test code added.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch konflux/mintmaker/devel/registry.redhat.io-rhel9-rhel-bootc-9.x

Review rate limit: 8/10 reviews remaining, refill in 10 minutes and 32 seconds.

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

@openshift-ci openshift-ci Bot requested review from bpradipt and pmores May 2, 2026 10:27
@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 2, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 2, 2026

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants