Update sylva-units-operator to v1.4.4 (main)

Sylva Renovate botrequested to merge
renovate/main-patch-sylva-units-operator into main

This MR contains the following updates:

Package Type Update Change
gitlab.com/sylva-projects/sylva-elements/sylva-units-operator Kustomization patch v1.4.3 → v1.4.4
registry.gitlab.com/sylva-projects/sylva-elements/sylva-units-operator patch v1.4.3 → v1.4.4
registry.gitlab.com/sylva-projects/sylva-elements/sylva-units-operator Kustomization patch v1.4.3 → v1.4.4

⚠️ 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.4: sylva-units-operator: v1.4.4

Compare Source

Merge Requests integrated in this release

12 merge requests were integrated in this repo between v1.4.3 and v1.4.4. These notes don't account for the MRs merged in secondary repos.

Sylva-units framework
  • Allow sylvaUnitsSource.type to be mutable !589 (issues: #​79)
Other
  • Pin gomod version in go-sbom image in CI !661
Other dependency upgrades
  • Update dependency go to v1.26.8 !659 !667
  • Update GO modules dependencies to v0.35.8 !663
  • Update pre-commit hook crate-ci/typos to v1.50.1 !665 !666 !669
CI
Internal tooling
  • pin tools version in golang's projects Makefile and use renovate to keep them up to date !645 area:CI
Contributors

3 people contributed.

Daniel Anton, Ishita Mittal, Mateo

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