11version : 2
2+
3+ # ⚠️ `target-branch: development` is load-bearing, not cosmetic.
4+ #
5+ # Without it Dependabot targets the repository DEFAULT branch, which is `main`.
6+ # `main` is currently **729 commits behind `development`** and carries an
7+ # entirely different lockfile, so the PRs Dependabot raised there were:
8+ #
9+ # • measured against a tree nobody develops on — the open alerts claimed
10+ # 5 critical / 51 high, while `development` actually had 1 critical /
11+ # 2 high (npm) and ZERO composer advisories; and
12+ # • ungated — `code-quality.yml` on `main` is a stale, self-contained
13+ # workflow, and PRs #368 and #369 collected **no check runs at all**
14+ # beyond a neutral CodeQL. A dependency PR that nothing builds is exactly
15+ # how this fleet previously shipped an unbuildable image for two months.
16+ #
17+ # Pointing Dependabot at `development` puts its PRs in front of the real
18+ # shared quality workflow (build, unit tests, SBOM, licence and audit legs).
19+ #
20+ # Trade-off, stated explicitly: GitHub only raises Dependabot SECURITY updates
21+ # against the default branch, so setting `target-branch` converts these to
22+ # VERSION updates. That is a net gain here — a version update on `development`
23+ # is verified and mergeable, whereas a security update on `main` was neither.
24+ # The alert list itself still tracks `main` and will only shrink as
25+ # `development` is released forward.
26+ #
27+ # Matches the fleet convention already in place on nldesign, decidesk,
28+ # openbuild, procest and shillinq.
29+
230updates :
331 - package-ecosystem : " npm"
432 directory : " /"
33+ target-branch : " development"
534 schedule :
635 interval : " weekly"
736 open-pull-requests-limit : 10
@@ -11,3 +40,34 @@ updates:
1140 - " *"
1241 exclude :
1342 - " @conduction/*"
43+
44+ # composer had no entry at all, so the only composer PRs this repo ever saw
45+ # were security updates against `main` (e.g. #369, which bumped twig to
46+ # 3.27.0 — a version `development` already had).
47+ #
48+ # default-days corrected 1 -> 2 and exclude added: this entry had a cooldown
49+ # window but no first-party exclusion, so a fresh conduction/* release would
50+ # have waited the same one day as any third-party package instead of being
51+ # exempt — the fleet-wide floor gate-93 (composer-cooldown-config) enforces
52+ # is 2 days plus a conduction/* exclude, matching the npm entry above's
53+ # exclude and the fleet's `conduction/hydra-gates` / `conduction/coding-standard`
54+ # first-party dependencies.
55+ - package-ecosystem : " composer"
56+ directory : " /"
57+ target-branch : " development"
58+ schedule :
59+ interval : " weekly"
60+ open-pull-requests-limit : 10
61+ cooldown :
62+ default-days : 2
63+ include :
64+ - " *"
65+ exclude :
66+ - " conduction/*"
67+
68+ - package-ecosystem : " github-actions"
69+ directory : " /"
70+ target-branch : " development"
71+ schedule :
72+ interval : " weekly"
73+ open-pull-requests-limit : 5
0 commit comments