Update workload-cluster-operator to v0.13.4 (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.3 -> v0.13.4
registry.gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator patch v0.13.3 -> v0.13.4
registry.gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator Kustomization patch v0.13.3 -> v0.13.4

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

Compare Source

Merge Requests integrated in this release

13 merge requests were integrated in this repo between v0.13.3 and v0.13.4. These notes don't account for the MRs merged in secondary repos.

Sylva-units framework
Workload cluster
Security
Other
  • Allow the go templating in valuesFrom repositories defined in presets !558 (issues: #​72)
Other dependency upgrades
  • Update pre-commit hook crate-ci/typos to v1.47.0 !547 !552 !556 !560
  • Update module github.com/fluxcd/source-controller/api to v1.8.5 !548 !554
  • Update GO modules dependencies to v0.35.5 !549
CI
  • Update dependency sylva-projects/sylva-elements/ci-tooling/ci-templates to v1.1.2 !550 renovate
  • Update docker.io/semgrep/semgrep container to v1.164.0 renovate !551 !559
Contributors

2 people contributed.

Francois Eleouet, 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