Update dependency metal3-io/cluster-api-provider-metal3 to v1.10.3 (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.10.2 -> v1.10.3

⚠️ 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.10.3

Compare Source

Changes since v1.10.2

🌱 Others

  • Uplift IPAM and BMO patch for release-1.10 (#​2871)
  • Bump CAPI to v1.10.7 (#​2866)
  • Add SKIP_NODE_IMAGE_PREPULL var in ci-e2e.sh (#​2855)
  • Bump golang to v1.24.8 (#​2848)
  • remove osv-scanner from release branches (#​2827)
  • Change interface names to predictable ones for Centos (#​2818)
  • Bump golang to v1.24.7 (#​2796)
  • Bump the kubernetes group to v0.32.9 (#​2772)
  • Bump github.com/metal3-io/baremetal-operator/apis from 0.10.2 to 0.10.3 in /hack/fake-apiserver (#​2775)
  • Bump github.com/metal3-io/cluster-api-provider-metal3 from 1.9.4 to 1.9.5 in /hack/fake-apiserver (#​2773)
  • Bump github.com/metal3-io/cluster-api-provider-metal3/api from 1.10.1 to 1.10.2 in /hack/fake-apiserver (#​2774)
  • Add logging to releaseAddressFromM3Pool function (#​2821)

The image for this release is: v1.10.3 Mariadb image tag is: capm3-v1.10.3

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