Update dependency https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-deployment-values.git to v0.5.62 (release-1.6)

This MR contains the following updates:

Package	Update	Change
https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-deployment-values.git	patch	0.5.60 -> 0.5.62

---

⚠️ Warning

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

---

Release Notes

sylva-projects/sylva-elements/ci-tooling/ci-deployment-values (https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-deployment-values.git)

v0.5.62: ci-deployment-values: 0.5.62

Compare Source

Merge Requests integrated in this release

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

Other

• Revert 4MDs on capo misc runs !354 CIconfiguration area:CI
• make light-deploy lighter !358 CIconfiguration area:CI

Contributors

2 people contributed.

Remi Le Trocquer, Thomas Morin

v0.5.61: ci-deployment-values: 0.5.61

Compare Source

Merge Requests integrated in this release

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

Other

• Fix miniserve logs redirect for leapmicro !348 area:CI
• CAPO misc set machine_deployments to 4 !350 CIconfiguration area:CI

Contributors

2 people contributed.

Bogdan Nicolae, Remi Le Trocquer

---

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 this update 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)