Skip to content

NO-JIRA: Update registry.redhat.io/ubi9/ubi Docker digest to 2323fcf#1095

Open
red-hat-konflux[bot] wants to merge 1 commit into
nextfrom
konflux/mintmaker/next/registry.redhat.io-ubi9-ubi
Open

NO-JIRA: Update registry.redhat.io/ubi9/ubi Docker digest to 2323fcf#1095
red-hat-konflux[bot] wants to merge 1 commit into
nextfrom
konflux/mintmaker/next/registry.redhat.io-ubi9-ubi

Conversation

@red-hat-konflux
Copy link
Copy Markdown
Contributor

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

This PR contains the following updates:

Package Type Update Change
registry.redhat.io/ubi9/ubi final digest 0879eaf2323fcf
registry.redhat.io/ubi9/ubi stage digest 0879eaf2323fcf

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

@red-hat-konflux red-hat-konflux Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels May 4, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@red-hat-konflux[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

This PR contains the following updates:

Package Type Update Change
registry.redhat.io/ubi9/ubi final digest 0879eaf3895254
registry.redhat.io/ubi9/ubi stage digest 0879eaf3895254

[!WARNING]
Some dependencies could not be looked up. Check the warning logs for more information.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 4, 2026
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/next/registry.redhat.io-ubi9-ubi branch from b8d04bd to 47951f5 Compare May 4, 2026 09:39
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label May 4, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 4, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci openshift-ci Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 4, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: red-hat-konflux[bot]

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 requested review from asm582 and mrunalp May 4, 2026 09:39
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: red-hat-konflux[bot]

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

@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/next/registry.redhat.io-ubi9-ubi branch from 47951f5 to 4ec9f12 Compare May 6, 2026 09:42
@red-hat-konflux red-hat-konflux Bot changed the title NO-JIRA: Update registry.redhat.io/ubi9/ubi Docker digest to 3895254 NO-JIRA: Update registry.redhat.io/ubi9/ubi Docker digest to edabf94 May 6, 2026
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/next/registry.redhat.io-ubi9-ubi branch from 4ec9f12 to ceb6398 Compare May 11, 2026 05:22
@red-hat-konflux red-hat-konflux Bot changed the title NO-JIRA: Update registry.redhat.io/ubi9/ubi Docker digest to edabf94 NO-JIRA: Update registry.redhat.io/ubi9/ubi Docker digest to 2323fcf May 11, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 11, 2026

@red-hat-konflux[bot]: all tests passed!

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.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant