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

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

Compare Source

Changes since v1.10.1

🐛 Bug Fixes

  • Delete child resources before machine (#​2752)
  • Bump github.com/go-viper/mapstructure/v2 from 2.3.0 to 2.4.0 in /test (#​2732)

🌱 Others

  • Bump IPAM v1.10.2 and BMO to v0.10.3 (#​2756)
  • Bump github.com/spf13/pflag from 1.0.7 to 1.0.10 (#​2750)
  • Bump CAPI to v1.10.6 (#​2743)
  • Bump actions/cache from 4.2.3 to 4.2.4 in the github-actions group (#​2738)
  • Uplift Ubuntu to 24.04 (#​2733)
  • Add IPA_BASEURI in ironic config to fix IPA download for release-1.10 (#​2730)
  • Bump the kubernetes group to v0.32.8 (#​2711)
  • bump golang to 1.24.6 (#​2692)
  • Bump the github-actions group with 2 updates (#​2682)
  • Fix trying to patch Metal3Data if it is deleted (#​2668)
  • E2E: Use cert-manager version from config (#​2629)
  • E2E: longer timeout for cert-manager (#​2628)
  • Bump github.com/metal3-io/cluster-api-provider-metal3 from 1.9.3 to 1.9.4 in /hack/fake-apiserver (#​2621)
  • Bump github.com/metal3-io/cluster-api-provider-metal3/api from 1.10.0 to 1.10.1 in /hack/fake-apiserver (#​2620)

♻️ Superseded or Reverted

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

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)

Edited by Sylva Renovate bot

Merge request reports