[red-hat-konflux-kflux-prd-rh02]

This PR contains the following updates:

File Dockerfiles/konflux/rpms.in.yaml:

Package	Change
emacs-filesystem	1:27.2-18.el9_8.3 -> 1:27.2-18.el9_9.1
libxslt	1.1.34-14.el9_8.1 -> 1.1.34-16.el9
python-unversioned-command	3.9.25-7.el9_8.6 -> 3.9.25-16.el9_9
acl	2.4.0-1.el9_8 -> 2.4.0-2.el9
dbus	1:1.12.20-8.el9 -> 1:1.12.20-10.el9
dbus-broker	28-9.el9_8 -> 28-10.el9_9
dbus-common	1:1.12.20-8.el9 -> 1:1.12.20-10.el9
dbus-libs	1:1.12.20-8.el9 -> 1:1.12.20-10.el9
expat	2.5.0-6.el9_8.7 -> 2.5.0-9.el9_9.4
libfdisk	2.37.4-25.el9 -> 2.37.4-28.el9_9
libseccomp	2.5.2-2.el9 -> 2.5.6-1.el9
pam	1.5.1-28.el9_8.1 -> 1.5.1-29.el9
procps-ng	3.3.17-14.el9 -> 3.3.17-15.el9
python3	3.9.25-7.el9_8.6 -> 3.9.25-16.el9_9
python3-libs	3.9.25-7.el9_8.6 -> 3.9.25-16.el9_9
systemd	252-67.el9_8.6 -> 252-79.el9_9
systemd-pam	252-67.el9_8.6 -> 252-79.el9_9
systemd-rpm-macros	252-67.el9_8.6 -> 252-79.el9_9
util-linux	2.37.4-25.el9 -> 2.37.4-28.el9_9
util-linux-core	2.37.4-25.el9 -> 2.37.4-28.el9_9
vim-filesystem	2:8.2.2637-26.el9_8.23 -> 2:8.2.2637-43.el9_9

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 04:59 AM (* 0-4 * * *)
• 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.

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

[openshift-ci]

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

I'm waiting for a ComplianceAsCode 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.

Due the failure and inability of me to rerun the Konflux jobs I'm dismissing this review.