Update sylva-units-operator to v1.4.1 (main) (patch)

This MR contains the following updates:

Package Type Update Change
gitlab.com/sylva-projects/sylva-elements/sylva-units-operator Kustomization patch v1.4.0 -> v1.4.1
registry.gitlab.com/sylva-projects/sylva-elements/sylva-units-operator patch v1.4.0 -> v1.4.1
registry.gitlab.com/sylva-projects/sylva-elements/sylva-units-operator Kustomization patch v1.4.0 -> v1.4.1

⚠️ Warning

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


Release Notes

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

v1.4.1: sylva-units-operator: v1.4.1

Compare Source

Merge Requests integrated in this release

11 merge requests were integrated in this repo between v1.3.4 and v1.4.1. These notes don't account for the MRs merged in secondary repos.

Security
  • Fix the sec vuln GO-2026-5026 by bumping golang.org/x/net version !622
Bug Fixes
  • Fix a bug in the insertion of a yaml inside another label at a given path !620
Other dependency upgrades
  • Update GO modules dependencies to v0.35.6 !614
  • Update pre-commit hook crate-ci/typos to v1.48.0 !627
  • Update dependency go to v1.26.5 !634
  • Update module k8s.io/apimachinery to v0.35.7 !636
CI
  • Update docker.io/semgrep/semgrep container to v1.169.0 renovate !613 !618 !626 !635
  • Update dependency sylva-projects/sylva-elements/ci-tooling/ci-templates to v1.1.3 !632 renovate
Contributors

1 person contributed.

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
Loading