Skip to content

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

Open
red-hat-konflux[bot] wants to merge 1 commit intoosc-release-v1.11from
konflux/mintmaker/osc-release-v1.11/registry.redhat.io-rhel9-rhel-bootc-9.x
Open

chore(deps): update registry.redhat.io/rhel9/rhel-bootc docker tag to v9.7-1773732460#1893
red-hat-konflux[bot] wants to merge 1 commit intoosc-release-v1.11from
konflux/mintmaker/osc-release-v1.11/registry.redhat.io-rhel9-rhel-bootc-9.x

Conversation

@red-hat-konflux
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
registry.redhat.io/rhel9/rhel-bootc final minor 9.5-1738698007 -> 9.7-1773732460

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-1773732460

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@openshift-ci openshift-ci bot requested review from bpradipt and wainersm March 22, 2026 01:37
@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 Mar 22, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 22, 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