Update dependency metal3-io/cluster-api-provider-metal3 to v1.12.5 (main)

Sylva Renovate botrequested to merge
renovate/main-patch-metal3 into main

This MR contains the following updates:

Package Update Change
metal3-io/cluster-api-provider-metal3 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.5

Compare Source

Changes since v1.12.4

⚠️ Vulnerability Fixes

🐛 Bug Fixes

  • Restrict namespace secret references in Metal3Machine (#​3343)
  • Restrict Metal3DataClaim templates to same namespace (#​3325)
  • Fix typo causing Metal3Cluster to reconcile on every status update (#​3331)
  • Fix logical operator in ConsumerRef validation (#​3319)

🌱 Others

  • Bump the kubernetes group to v0.34.8 (#​3389)
  • Bump Go version to 1.25.10 (#​3371)
  • Bump github.com/metal3-io/baremetal-operator/apis from 0.11.6 to 0.11.7 in /hack/fake-apiserver (#​3339)
  • Bump github.com/metal3-io/cluster-api-provider-metal3/api from 1.11.6 to 1.11.7 in /hack/fake-apiserver (#​3338)

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

🔕 Ignore: Close this MR and you won't be reminded about this update again.

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

Merge request reports