From 4268dda22daaa23ee096f6ec122c028103df55c2 Mon Sep 17 00:00:00 2001 From: Conduction Release Bot Date: Sun, 30 Aug 2026 23:13:10 +0200 Subject: [PATCH] docs(dependabot): correct the vue-router holdback to what was measured The comment claimed these apps "cannot resolve it at all". That is not what the evidence shows, and a comment that overstates its case is worse than none: the next person reads it, tries vue-router 5 somewhere it works, and stops trusting the file. Measured across four apps: integriq and zaakafhandelapp fail their build on `Can't resolve 'vue-router'`, while openregister and learniq build clean on 5.3.0. The holdback still stands, for the honest reason rather than the overstated one: a major that breaks some apps and not others cannot be merged unattended, and the difference between them is not yet understood. No behaviour change. The ignore rule is unchanged; only the reasoning is. --- .github/dependabot.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 786b6317..0535df19 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -27,8 +27,11 @@ updates: - dependency-name: "typescript" update-types: ["version-update:semver-major"] # vue-router 5 peers `vite: ^7.3.0 || ^8.0.0` and expects a Vite - # toolchain. These apps build with webpack, which cannot resolve it at - # all: the build dies on `Can't resolve 'vue-router'`. Adopting it is a + # toolchain. Measured, not assumed, and the result is SPLIT: integriq and + # zaakafhandelapp fail their build on `Can't resolve 'vue-router'`, while + # openregister and learniq build clean on 5.3.0. Held because a bump that + # breaks some apps and not others cannot be merged unattended, and the + # difference is not yet understood. Adopting it fleet-wide is a # Vite migration, not a bump. versioniq is already on Vite and is the # natural pilot. - dependency-name: "vue-router"