Update sylva-units-operator to v1.3.7 (release-1.7)

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

This MR contains the following updates:

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

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

Compare Source

Merge Requests integrated in this release

2 merge requests were integrated in this repo between v1.3.6 and v1.3.7. These notes don't account for the MRs merged in secondary repos.

Other
CI
  • Update dependency sylva-projects/sylva-elements/ci-tooling/ci-templates to v1.1.5 (release-1.3-sylva-1.7) !650 renovate
Contributors

1 person contributed.

Francois Eleouet

v1.3.6: sylva-units-operator: v1.3.6

Compare Source

Merge Requests integrated in this release

1 merge request was integrated in this repo between v1.3.5 and v1.3.6. These notes don't account for the MRs merged in secondary repos.

Other
  • [backport-1.7]: sylva-units-operator can't patch events correctly !652 backport (issues: #​106)
Contributors

1 person contributed.

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)

Edited by Sylva Renovate bot

Merge request reports