Skip to content

chore(release): 4.1.0 #55

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 29, 2026
Merged

chore(release): 4.1.0 #55

Show file tree
Hide file tree
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
17 changes: 15 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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
Expand Down
13 changes: 7 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).

---

Expand Down Expand Up @@ -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).
Expand Down
3 changes: 2 additions & 1 deletion SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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` |
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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",
Expand Down