Update workload-cluster-operator to v0.14.6 (main)
This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator | Kustomization | patch | v0.14.5 → v0.14.6 |
| registry.gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator | patch | v0.14.5 → v0.14.6 |
|
| registry.gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator | Kustomization | patch | v0.14.5 → v0.14.6 |
⚠️ WarningSome 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.6: workload-cluster-operator: v0.14.6
Merge Requests integrated in this release
11 merge requests were integrated in this repo between v0.14.5 and v0.14.6. 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.5 !635 renovate
- Update sylvactl to v0.15.5 !640 release-typepatch renovate
Workload cluster
Other dependency upgrades
- Update GO modules patch to v0.37.1 !653 release-typepatch
- Update GO minor - kubernetes !645 release-typepatch
- Update GO minor - test !646 release-typepatch
CI
- Update GO tools dependencies !648 release-typenone renovate
- add _typos.toml to exclude go.mod and go.sum from typos checks !651
- Update GO tools - codegen !647 release-typenone renovate
Internal tooling
- Regroup fluxcd updates in a single MR !641 area:CI
- Regenerate manifests on codegen updates !650 area:CI
Contributors
2 people contributed.
Configuration
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
- 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)