feat!: raise the VS Code floor to 1.136

.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.134.0` puts the floor lower still. A bump past that
+      # `engines.vscode: ^1.136.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,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.5.0] - 2026-09-07
+
+**Breaking: VS Code 1.136 or later is now required**, up from 1.134, in step with
+`@types/vscode` moving to `~1.136.0`. The two have to move together — `vsce`
+refuses to package an extension whose `@types/vscode` outruns its
+`engines.vscode`, and raising only the types would let code compile against an
+API the declared floor does not have.
+
+The floor is inherited: `@kkdev92/vscode-ext-kit` 5.0.0 raised its own
+`engines.vscode` to `^1.136.0`, and every extension built on it declares at least
+the same. Nothing this extension does changed — pasting, saving and the image
+handling behave exactly as in 0.4.x. Installations on an older VS Code keep
+0.4.x and stop receiving updates.
+
+### Changed
+
+- **Breaking:** `engines.vscode` raised from `^1.134.0` to `^1.136.0`, with
+  `@types/vscode` at `~1.136.0` to match.
+- `@kkdev92/vscode-ext-kit` `^4.1.0` → `^5.0.0`. The only change in that major is
+  the VS Code floor; the API it exposes is byte-for-byte what 4.1.1 exposed.
+
 ### Fixed
 
 - **The Marketplace version badge could render as a broken image.** The host
@@ -325,7 +346,8 @@ Initial release.
   (PNG/JPEG/WebP) and quality.
 - Path validation and sanitization to keep saved files inside the workspace.
 
-[Unreleased]: https://github.com/kkdev92/clipshot/compare/v0.4.1...HEAD
+[Unreleased]: https://github.com/kkdev92/clipshot/compare/v0.5.0...HEAD
+[0.5.0]: https://github.com/kkdev92/clipshot/compare/v0.4.1...v0.5.0
 [0.4.1]: https://github.com/kkdev92/clipshot/compare/v0.4.0...v0.4.1
 [0.4.0]: https://github.com/kkdev92/clipshot/compare/v0.3.2...v0.4.0
 [0.3.2]: https://github.com/kkdev92/clipshot/compare/v0.3.1...v0.3.2

CONTRIBUTING.md

@@ -12,7 +12,7 @@ Please be respectful and constructive in all interactions.
 
 - Node.js 22.12 or later (what CI builds on)
 - npm 10.x or later
-- VS Code 1.134.0 or later — the minimum the extension declares
+- VS Code 1.136.0 or later — the minimum the extension declares
 - Git
 
 ### Development Setup

README.md

@@ -263,7 +263,7 @@ For the full policy and for vulnerability reporting, see [SECURITY.md](SECURITY.
 
 ## Platform Requirements
 
-- **VS Code 1.134 or later**
+- **VS Code 1.136 or later**
 - Windows, macOS or Linux, on x64 or ARM64
 
 | Platform | Needs |
@@ -280,9 +280,9 @@ instead of all six. VS Code picks the right one for you.
 CI runs the test suite on Windows, macOS and Linux, and builds and verifies all
 six.
 
-> **Upgrading?** The minimum VS Code version is now 1.134 — it was 1.125 from
-> 0.3.0, and 1.96 before that. Older installations keep the version they have
-> and stop receiving updates.
+> **Upgrading?** The minimum VS Code version is now 1.136 — it was 1.134 from
+> 0.4.0, 1.125 from 0.3.0, and 1.96 before that. Older installations keep the
+> version they have and stop receiving updates.
 
 ---