From 83a5c33cb14644c852cdada132aabdc4bbfbd809 Mon Sep 17 00:00:00 2001 From: kkdev92 Date: Sat, 29 Aug 2026 01:30:34 +0900 Subject: [PATCH] docs(changelog): record what 0.4.0 actually ships Twenty-three commits landed since v0.3.0 and the 0.4.0 section described four of them. Most of the rest are CI and repository hygiene that a changelog should not carry, but three were real and missing: the move to Node 24, the step from `@kkdev92/vscode-ext-kit` ^3.0.0-alpha.1 to the released ^3.0.0, and the eslint and typescript-eslint bumps. Every version here was read back out of package-lock.json rather than copied from the pull request that bumped it. Co-Authored-By: Claude Opus 5 (1M context) --- CHANGELOG.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 92a0f88..eb024b2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -21,7 +21,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 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. +- **Building this extension now needs Node.js 24** (`engines.node` `>=22.12.0` + → `>=24.0.0`, `@types/node` 22 → 24). This is a contributor requirement, not a + user one — VS Code supplies the Node that runs the extension. + +- `@kkdev92/vscode-ext-kit` moved from `^3.0.0-alpha.1` to the released `^3.0.0`. + 0.3.0 shipped against an alpha; this is the same framework, out of prerelease. + +- Dev dependencies: `vitest` and `@vitest/coverage-v8` 4.1.10 → 4.1.11, `eslint` + 10.8.0 → 10.9.1, `typescript-eslint` 8.65.0 → 8.68.0. `lint` also fails on + warnings now, so a warning cannot accumulate unnoticed. - `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