Skip to content

docs(changelog): record what 0.4.0 actually ships #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kkdev92 merged 1 commit into from
Aug 28, 2026
Merged

docs(changelog): record what 0.4.0 actually ships #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down