chore(deps): update registry.access.redhat.com/ubi9/python-312 docker tag to v9.8-1784826605

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
registry.access.redhat.com/ubi9/python-312	stage	patch	9.8-1780506588 → 9.8-1784826605

---

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 is behind base branch, 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]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

Walkthrough

The builder stage base image in the Dockerfile is updated from ubi9/python-312:9.8-1780506588 to ubi9/python-312:9.8-1781757943. No other build steps or runtime stage configuration are changed.

Changes

Base Image Update

Layer / File(s)	Summary
Builder stage base image tag update Dockerfile	The FROM image tag for the builder stage is bumped to ubi9/python-312:9.8-1781757943; all other Dockerfile instructions remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title describes the Docker image tag update, which matches the main change, even though the exact version differs from the diff.
Description check	✅ Passed	The description is directly related to the Docker image tag update and the automated dependency bump.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/master/registry.access.redhat.com-ubi9-python-312-9.x

---

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

[coderabbitai]

🧹 Nitpick comments (1)

Dockerfile (1)

1-1: Verify the new base image is accessible and review security updates from Red Hat.

The builder stage base image update from 9.8-1780506588 to 9.8-1781023618 is a valid patch-level update within RHEL 9.8. To ensure this change is safe:

1. Verify the image is accessible in your deployment environment (may require Red Hat registry authentication)
2. Check Red Hat Errata advisories (RHSA/RHBA) near the build date for security fixes and changes included in this build
3. Review the image details in the Red Hat Ecosystem Catalog at https://catalog.redhat.com/en/software/containers/ubi9/python-312/

Note: There is version drift between the builder stage (build 1781023618) and runtime stage (build 1780378819). Confirm this is intentional or consider updating the runtime stage for consistency.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Dockerfile` at line 1, Verify that the updated builder stage base image using
build identifier 1781023618 is accessible in your deployment environment and
review Red Hat Errata advisories (RHSA/RHBA) published around the build date to
understand what security fixes and changes are included in this patch update.
Additionally, check the Red Hat Ecosystem Catalog to review the image details
and specifications. Finally, address the version drift noted between the builder
stage (using build 1781023618) and the runtime stage (using build 1780378819) by
either confirming this difference is intentional for your use case or updating
the runtime stage base image to use a matching or compatible build identifier
for consistency.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@Dockerfile`:
- Line 1: Verify that the updated builder stage base image using build
identifier 1781023618 is accessible in your deployment environment and review
Red Hat Errata advisories (RHSA/RHBA) published around the build date to
understand what security fixes and changes are included in this patch update.
Additionally, check the Red Hat Ecosystem Catalog to review the image details
and specifications. Finally, address the version drift noted between the builder
stage (using build 1781023618) and the runtime stage (using build 1780378819) by
either confirming this difference is intentional for your use case or updating
the runtime stage base image to use a matching or compatible build identifier
for consistency.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 1a3272d1-5ad2-492c-99c0-2fca783bfb74

📥 Commits

Reviewing files that changed from the base of the PR and between ce38869 and 62fb339.

📒 Files selected for processing (1)

• Dockerfile