Update dependency sylva-projects/sylva-elements/ci-tooling/ci-components/scheduled-pipeline-report to v1.1.1 (main)

Sylva Renovate botrequested to merge
renovate/main-sylva-projects-sylva-elements-ci-tooling-ci-components-scheduled-pipeline-report-1.1.x into main

This MR contains the following updates:

Package Type Update Change
sylva-projects/sylva-elements/ci-tooling/ci-components/scheduled-pipeline-report repository patch 1.1.0 → 1.1.1

⚠️ Warning

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

Release Notes

sylva-projects/sylva-elements/ci-tooling/ci-components/scheduled-pipeline-report (sylva-projects/sylva-elements/ci-tooling/ci-components/scheduled-pipeline-report)

v1.1.1

Compare Source

1.1.1
🐛 Bug Fixes
  • Add short summary of sylvactl watch conclusion on failed jobs (!15) by Cristian Manda
🔄 Other Changes
  • Update pre-commit hook sylva-projects/sylva-elements/ci-tooling/ci-components/renovate to v1.0.4 (main) (!14) by Sylva Renovate bot
  • Update pre-commit hook sylva-projects/sylva-elements/ci-tooling/ci-components/renovate to v1.0.3 (main) (!13) by Sylva Renovate bot
  • Update dependency sylva-projects/sylva-elements/ci-tooling/ci-components/pre-commit to v1.0.2 (main) (!12) by Sylva Renovate bot
  • Update dependency sylva-projects/sylva-elements/ci-tooling/ci-components/docker-build to v1.0.6 (main) (!11) by Sylva Renovate bot
  • use renovate component and move gitleaks to pre-commit (!10) by Jonathan GAYVALLET

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

Merge request reports