Update workload-cluster-operator to v0.13.3 (main) (patch)

This MR contains the following updates:

Package Type Update Change
gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator Kustomization patch v0.13.2 -> v0.13.3
registry.gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator patch v0.13.2 -> v0.13.3
registry.gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator Kustomization patch v0.13.2 -> v0.13.3

⚠️ 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.13.3: workload-cluster-operator: v0.13.3

Compare Source

Merge Requests integrated in this release

21 merge requests were integrated in this repo between v0.13.2 and v0.13.3. 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.2.5 renovate !523 !529
Workload cluster
Other dependency upgrades
  • Update pre-commit hook crate-ci/typos to v1.46.0 !527 !532 !540 !542
  • Update module k8s.io/apimachinery to v0.35.4 !533
  • Update GO modules dependencies to v0.35.4 !534
  • Update module github.com/onsi/ginkgo/v2 to v2.28.2 !538
  • Update dependency fluxcd/source-controller to v1.8.1 !503
  • Update module github.com/fluxcd/source-controller/api to v1.8.3 !545
  • Update GO modules dependencies !541
CI
Contributors

2 people contributed.

Priya Goyal, Vladimir Braquet


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

Loading