From 5dc33cc157b952e9bae1ed192683dcadc7c0f55a Mon Sep 17 00:00:00 2001 From: FROWNINGdev Date: Mon, 24 Aug 2026 23:15:04 +0500 Subject: [PATCH] chore(deps): pin @types/vscode to engines.vscode via dependabot ignore vsce refuses to package the extension when @types/vscode outruns the engine declared in package.json: @types/vscode ^1.134.0 greater than engines.vscode ^1.85.0. Either upgrade engines.vscode or use an older @types/vscode version That is what turned the `build` job red on PR #89 (1.125.0 -> 1.134.0). Raising engines.vscode to match would silently drop every user on an older VS Code, so the types are the side that has to stay pinned. Ignore all version updates for @types/vscode. It now moves only by hand, in the same commit that raises engines.vscode. --- .github/dependabot.yml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index c891ff7..b1e30a8 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -43,6 +43,14 @@ updates: ignore: - dependency-name: "typescript" update-types: ["version-update:semver-major"] + # @types/vscode is not a normal dev dep: it must track engines.vscode + # (currently ^1.85.0), not latest. vsce refuses to package when the + # types outrun the declared engine -- + # '@types/vscode ^1.134.0 greater than engines.vscode ^1.85.0' + # -- which is exactly what turned PR #89 red on 2026-08-24. Raise this + # by hand, together with engines.vscode, when we deliberately drop + # support for older VS Code builds. + - dependency-name: "@types/vscode" # Docker — root Dockerfile bakes the GHCR image. - package-ecosystem: "docker"