From 7762520aa1952e9d24258b0311bbef2325bc20f9 Mon Sep 17 00:00:00 2001 From: Conduction Release Bot Date: Sun, 30 Aug 2026 22:31:35 +0200 Subject: [PATCH] chore(dependabot): hold back vue-router 5 as well 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'` from src and from @nextcloud/vue's own chunks. Adopting it is a Vite migration, not a version bump. Dependabot proposed it across 8 repositories in a single run, and merging any one of them takes that app's build from green to red with no code change that can fix it. versioniq already builds with Vite and is the natural pilot if the fleet does move. Lift this when an app's toolchain can actually take it. --- .github/dependabot.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 7a8476c5..786b6317 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -26,6 +26,13 @@ updates: ignore: - 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 + # Vite migration, not a bump. versioniq is already on Vite and is the + # natural pilot. + - dependency-name: "vue-router" + update-types: ["version-update:semver-major"] - dependency-name: "webpack-cli" update-types: ["version-update:semver-major"] - dependency-name: "@babel/core"