Update workload-cluster-operator to v0.14.5 (main)

Sylva Renovate botrequested to merge
renovate/main-patch-workload-cluster-operator into main

This MR contains the following updates:

Package Type Update Change
gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator Kustomization patch v0.14.4 → v0.14.5
registry.gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator patch v0.14.4 → v0.14.5
registry.gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator Kustomization patch v0.14.4 → v0.14.5

⚠️ Warning

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

Release Notes

sylva-projects/sylva-elements/workload-cluster-operator (gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator)

v0.14.5: workload-cluster-operator: v0.14.5

Compare Source

Merge Requests integrated in this release

6 merge requests were integrated in this repo between v0.14.4 and v0.14.5. These notes don't account for the MRs merged in secondary repos.

Sylva-units framework
  • Update dependency gitlab.com/sylva-projects/sylva-elements/sylva-units-operator to v1.4.4 !629 renovate
Workload cluster
  • Make spec.controlPlane and spec.machineDeployments optional on SylvaWorkloadCluster !625 (issues: #​83)
Other dependency upgrades
  • Update pre-commit hook crate-ci/typos to v1.50.2 !634
CI
Internal tooling
Contributors

2 people contributed.

Loic Nicolle, Priya Goyal

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)

Merge request reports