Update heat-operator to v0.5.2 (main)

This MR contains the following updates:

Package	Type	Update	Change
gitlab.com/sylva-projects/sylva-elements/heat-operator	Kustomization	patch	0.5.1 → 0.5.2
registry.gitlab.com/sylva-projects/sylva-elements/heat-operator		patch	0.5.1 → 0.5.2
registry.gitlab.com/sylva-projects/sylva-elements/heat-operator	Kustomization	patch	0.5.1 → 0.5.2

---

⚠️ Warning

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

---

Release Notes

sylva-projects/sylva-elements/heat-operator (gitlab.com/sylva-projects/sylva-elements/heat-operator)

v0.5.2: heat-operator: 0.5.2

Compare Source

Merge Requests integrated in this release

16 merge requests were integrated in this repo between 0.5.1 and 0.5.2. These notes don't account for the MRs merged in secondary repos.

Other dependency upgrades

• Update module k8s.io/apimachinery to v0.35.7 !367
• Update module github.com/go-logr/logr to v1.4.4 !369
• Update GO modules dependencies to v0.35.7 !371
• Update GO modules dependencies !357
• Update GO modules dependencies !374

CI

• Update dependency sylva-projects/sylva-elements/ci-tooling/ci-templates to v1.1.3 renovate !363 !365
• Update sylva-elements/container-images/ci-image container to v1.10.4 renovate !351 !362
• Update docker.io/semgrep/semgrep container to v1.172.0 renovate !348 !366 !368 !370 !372 !373

Internal tooling

• Use go-toolkit component !378 area:CI

Contributors

1 person contributed.

Loic Nicolle

---

Configuration

📅 Schedule: (UTC)

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