Update metal3 (main) (patch)

This MR contains the following updates:

Package	Update	Change
metal3-io/cluster-api-provider-metal3	patch	v1.12.5 -> v1.12.6
metal3-io/ip-address-manager	patch	v1.12.4 -> v1.12.5

---

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

metal3-io/cluster-api-provider-metal3 (metal3-io/cluster-api-provider-metal3)

v1.12.6

Compare Source

Changes since v1.12.5

🌱 Others

• Bump IPAM 1.12.5 and BMO 0.12.5 (#​3493)
• Bump CAPI to 1.12.9 (#​3487)
• bump containerd/containerd to 1.17.33 (#​3475)
• Use proper IPA cache address (#​3470)
• Switch from docker to moby dependencies (#​3467)
• Bump the kubernetes to v0.34.9 (#​3465)
• Bump go to 1.25.11 (#​3435)
• Fix ownerRef chain for IPAddress in e2e tests (#​3425)
• Bump github.com/metal3-io/cluster-api-provider-metal3/api from 1.11.7 to 1.11.8 in /hack/fake-apiserver (#​3415)

♻️ Superseded or Reverted

• #​3448 #​3414

The image for this release is: v1.12.6

Thanks to all our contributors! 😊

metal3-io/ip-address-manager (metal3-io/ip-address-manager)

v1.12.5

Compare Source

Changes since v1.12.4

🐛 Bug Fixes

• Simplify ownerRefs for IPAddresses (#​1407)

🌱 Others

• Bump CAPI to 1.12.9 (#​1472)
• Bump the kubernetes group to v0.34.9 (#​1468)
• Bump Go version to 1.25.11 (#​1432)
• Bump the kubernetes group from 0.34.7 to 0.34.8 (#​1421)

♻️ Superseded or Reverted

• #​1456, #​1422, #​1412

The container image for this release is: v1.12.5

Thanks to all our contributors! 😊

---

Configuration

📅 Schedule: 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 MR becomes conflicted, or you tick the rebase/retry checkbox.

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

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot Sylva instance.

CI configuration couldn't be handle by MR description. A dedicated comment has been posted to control it.

If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)