feat!: bump the npm-minor-patch group, raising engines.vscode to ^1.134.0

.github/dependabot.yml

@@ -25,7 +25,7 @@ updates:
       # @types/node majors: these types decide what Node API the code may compile
       # against, so they must not exceed the runtime. VS Code 1.132's extension
       # host runs Node 24.18.0 (measured, via ELECTRON_RUN_AS_NODE), and
-      # `engines.vscode: ^1.125.0` puts the floor lower still. A bump past that
+      # `engines.vscode: ^1.134.0` puts the floor lower still. A bump past that
       # passes CI — nothing reaches for a newer API *yet* — which is precisely why
       # CI cannot be what catches it. Same rule as @types/vscode, where the types
       # floor is also the ceiling. Revisit when the host moves.

CHANGELOG.md

@@ -7,6 +7,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Changed
+
+- **Breaking: VS Code 1.134 or later is now required**, up from 1.125, in step
+  with `@types/vscode` moving to `~1.134.0`. The two have to move together —
+  `vsce` refuses to package an extension whose `@types/vscode` is newer than its
+  `engines.vscode`, which is what the grouped dependency update ran into:
+  `@types/vscode ~1.134.0 greater than engines.vscode ^1.125.0`. The rule is
+  right, because types above the floor let code compile against an API the
+  declared minimum does not have.
+
+  DefinitelyTyped had been stuck at 1.125.0 for months against a stable line
+  already past 1.131; it has now caught up to 1.134.0, one release behind the
+  current 1.135.
+
+- Dev dependencies: `vitest` and `@vitest/coverage-v8` 4.1.10 → 4.1.11.
+
+- `CONTRIBUTING.md` said Node.js ≥ 22.12 while `engines.node` and CI both
+  require 24, and cited the floor of `@kkdev92/vscode-ext-kit` 2.0 when the
+  dependency has been `^3.0.0` for some time. Both corrected.
+
 ### Fixed
 
 - **`quickUtils.logLevel` now does something.** It was declared, described in

CONTRIBUTING.md

@@ -10,8 +10,8 @@ This project follows the [Contributor Covenant](CODE_OF_CONDUCT.md). By particip
 
 ### Prerequisites
 
-- Node.js ≥ 22.12 (matches `engines.node`, which follows the kit's floor, and CI)
-- VS Code ≥ 1.125 (the floor `@kkdev92/vscode-ext-kit` 2.0 requires)
+- Node.js ≥ 24 (matches `engines.node` and what CI runs)
+- VS Code ≥ 1.134 (the floor `@kkdev92/vscode-ext-kit` 3.x requires)
 - Nothing else — no Java, no Docker, no service credentials
 
 ### Development Setup

README.md

@@ -285,17 +285,17 @@ threat model and for vulnerability reporting, see [SECURITY.md](SECURITY.md).
 
 ## Platform Requirements
 
-- VS Code 1.125 or later
+- VS Code 1.134 or later
 - Windows, macOS or Linux, on x64 or ARM64
 
 CI runs the test suite on Windows, macOS and Linux (x64 on Windows and Linux,
 ARM64 on macOS). The extension is plain JavaScript, so other combinations are
 expected to work; please open an issue if one does not.
 
-> The 1.125 floor comes from `@kkdev92/vscode-ext-kit`, whose `engines.vscode` is
-> `^1.125.0` — the newest `@types/vscode` there is, and so the newest API it can
+> The 1.134 floor comes from `@kkdev92/vscode-ext-kit`, whose `engines.vscode` is
+> `^1.134.0` — the newest `@types/vscode` there is, and so the newest API it can
 > name. Quick Utils 0.1.x works on VS Code 1.96 and up; installations older than
-> 1.125 keep that version and simply stop receiving updates.
+> 1.134 keep the version they have and simply stop receiving updates.
 
 ---