From 9fb2b1db297a5d52154439011a14a83d490072b7 Mon Sep 17 00:00:00 2001 From: kkdev92 <112151103+kkdev92@users.noreply.github.com> Date: Sun, 30 Aug 2026 01:11:11 +0900 Subject: [PATCH] chore(release): 4.1.0 --- CHANGELOG.md | 17 +++++++++++++++-- README.md | 13 +++++++------ SECURITY.md | 3 ++- package-lock.json | 4 ++-- package.json | 2 +- 5 files changed, 27 insertions(+), 12 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index bf96f77..c4f39c0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,7 +6,19 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). From 1.0.0 onward this project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Pre-1.0 releases followed it in spirit; their breaking changes are marked **Breaking**. -## [Unreleased] +## [4.1.0] - 2026-08-30 + +**A minor about seeing what the framework already knows.** Everything here is +additive: the API `4.0.1` exposed is unchanged, the VS Code floor stays at +`^1.134.0`, and the one behaviour change — `defineExtension` refusing a second +activation after `deactivate` — is visible only to a test that activated one +result twice. The theme is introspection and tooling: a compiled plan as JSON, +a preflight failure as data, a shutdown timeout that names what held it, a +command-line tool that reads a built extension's plan and checks its manifest, +an API reference generated from the JSDoc, and a step-by-step migration guide +from 2.x. Each piece was run against a real extension before it landed, and two +of the entries below exist because that turned up something the framework could +not yet say. ### Added @@ -1160,7 +1172,8 @@ platform support, toolchain currency, and release supply chain. Initial public release. -[Unreleased]: https://github.com/kkdev92/vscode-ext-kit/compare/v4.0.1...HEAD +[Unreleased]: https://github.com/kkdev92/vscode-ext-kit/compare/v4.1.0...HEAD +[4.1.0]: https://github.com/kkdev92/vscode-ext-kit/compare/v4.0.1...v4.1.0 [4.0.1]: https://github.com/kkdev92/vscode-ext-kit/compare/v4.0.0...v4.0.1 [4.0.0]: https://github.com/kkdev92/vscode-ext-kit/compare/v3.0.0...v4.0.0 [3.0.0]: https://github.com/kkdev92/vscode-ext-kit/compare/v3.0.0-alpha.3...v3.0.0 diff --git a/README.md b/README.md index 268e722..e37672b 100644 --- a/README.md +++ b/README.md @@ -12,11 +12,12 @@ runs it, and tears it down through exactly one path. _Built for extensions big enough that "what does this thing actually register?" has stopped being obvious._ -> **Status:** `4.0.1` — the current release. It is `3.0.0` with the VS Code -> floor raised to `^1.134.0` and a fix in the tree-view adapter; the API is -> unchanged. 2.x was a utility library with a different shape; it continues on -> `v2-maintenance` and anything pinned to `^2.x` is unaffected. See -> [Coming from 2.x](#coming-from-2x). +> **Status:** `4.1.0` — the current release. It adds introspection and tooling +> to `4.0.1` — a plan as JSON, a preflight failure as data, a command-line +> tool, an API reference, a migration guide — and changes nothing that existed; +> the VS Code floor stays `^1.134.0`. 2.x was a utility library with a +> different shape; it continues on `v2-maintenance` and anything pinned to +> `^2.x` is unaffected. See [Coming from 2.x](#coming-from-2x). --- @@ -456,7 +457,7 @@ This is a personal project maintained in spare time. It is active, but support is best-effort: I'll do my best to review issues and PRs, and releases may be a bit slow sometimes — thank you for your patience. -`4.0.1` is the current release and holds `latest` on npm, so a fresh +`4.1.0` is the current release and holds `latest` on npm, so a fresh `npm install` gets the framework. `2.x` continues on `v2-maintenance` and still takes bug fixes; anything pinned to `^2.x` resolves there and is unaffected. Breaking changes are listed in the [CHANGELOG](CHANGELOG.md). diff --git a/SECURITY.md b/SECURITY.md index 869e314..5bb57e8 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -4,7 +4,8 @@ | Version | Supported | Notes | | --------------- | --------- | ----------------------------------------------- | -| `4.0.x` | ✅ | `latest` on npm | +| `4.1.x` | ✅ | `latest` on npm | +| `4.0.x` | ✅ | same API; `4.1.x` only adds to it | | `3.0.x` | ✅ | same API as 4.0.x, VS Code floor `^1.125.0` | | `2.1.x` | ✅ | maintained on `v2-maintenance`; `^2.x` resolves here | | `2.0.x` | ❌ | upgrade to `2.1.x` | diff --git a/package-lock.json b/package-lock.json index 942aad0..2c95375 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@kkdev92/vscode-ext-kit", - "version": "4.0.1", + "version": "4.1.0", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@kkdev92/vscode-ext-kit", - "version": "4.0.1", + "version": "4.1.0", "license": "MIT", "bin": { "vscode-ext-kit": "bin/vscode-ext-kit.mjs" diff --git a/package.json b/package.json index 0b43953..901ce98 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@kkdev92/vscode-ext-kit", - "version": "4.0.1", + "version": "4.1.0", "description": "A type-safe application framework for VS Code extension development", "author": { "name": "kkdev92",