Update registry.redhat.io/ubi9/ubi-minimal Docker tag to v9.8-1788939036

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
registry.redhat.io/ubi9/ubi-minimal	final	patch	9.8-1786987521 → 9.8-1788939036

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 0dbc34da-7fce-4657-aba4-bfd76edca014

📥 Commits

Reviewing files that changed from the base of the PR and between 1d6b214 and d82167e.

📒 Files selected for processing (3)

• Dockerfile
• bundle.Dockerfile
• hack/bundle.Dockerfile

Included review availability: Your plan provides up to 12 included reviews per hour; 5 remain after this review.

---

📝 Walkthrough

Walkthrough

The runtime and bundle Dockerfiles now use UBI9 image build 9.8-1788939036. Other build and runtime instructions remain unchanged.

Changes

UBI9 base image refresh

Layer / File(s)	Summary
Update UBI9 image references Dockerfile, bundle.Dockerfile, hack/bundle.Dockerfile	All three Dockerfiles now reference UBI9 image build 9.8-1788939036.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to d8216

This refreshes the UBI9 minimal base image consistently for runtime and bundle images. No current merge-blocking risk remains.

Suggested reviewers: blublinsky, sriroopar

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the UBI minimal Docker image tag to v9.8-1788939036.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/main/registry.redhat.io-ubi9-ubi-minimal-9.x

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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:

• OWNERS

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

[openshift-ci]

@red-hat-konflux[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/fips-image-scan-operator	d82167e	link	true	/test fips-image-scan-operator

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.