kandown 0.33.2 → 0.33.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +22 -0
- package/bin/kandown.js +1070 -143
- package/bin/tui.js +138 -74
- package/dist/index.html +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,27 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.33.4 — 2026-07-21 — "Daemon Update Recovery"
|
|
4
|
+
|
|
5
|
+
- **Fixed**: **Default `kandown` Launch Reusing Stale Daemons** — running `kandown` now validates the already-running project daemon version before reusing it. If the daemon is missing a version or is running a different CLI version than the current command, Kandown safely stops it and starts a fresh daemon from the active CLI so the browser opens the current web app instead of stale in-memory code.
|
|
6
|
+
- **Fixed**: **Web UI Auto-Update Not Taking Effect Immediately** — successful `/api/update/apply` calls now schedule a detached daemon restart after the HTTP success response is sent. This makes one-click Web UI updates actually switch the local server process to the newly installed package instead of requiring a manual daemon stop/start.
|
|
7
|
+
- **Fixed**: **Auto-Updater False Success Across Multiple Node Prefixes** — global package update attempts now verify the resolved `kandown --version` after each package-manager install command. If `npm`, `pnpm`, `yarn`, or `bun` updates a different global prefix than the executable on PATH, the updater keeps trying fallbacks and no longer reports success while the active command remains stale.
|
|
8
|
+
- **Changed**: **Daemon Health Metadata** — daemon status checks now read and propagate the remote daemon version from `/api/daemon`, keeping CLI-side restart decisions aligned with the process that is actually serving the project.
|
|
9
|
+
- **Changed**: **Update Route Messaging** — the update API success message now explicitly says the daemon is restarting, making the expected short reconnect window clearer for the Web UI.
|
|
10
|
+
|
|
11
|
+
## 0.33.3 — 2026-07-21 — "CLI Recovery"
|
|
12
|
+
|
|
13
|
+
- **Fixed**: **Default `kandown` Launch Regression** — restored the pre-split zero-setup startup flow where running `kandown` inside any project automatically initializes `.kandown/` when needed, refreshes the web bundle, starts the per-project daemon, and enters the normal board launch path.
|
|
14
|
+
- **Fixed**: **Global Flag Command Parsing** — repaired CLI dispatch so global flags such as `--no-update-check`, `--no-open`, `--path`, and `--port` no longer get mistaken for commands. This fixes the auto-updater restart path and the daemon spawn path that launches `--no-update-check daemon run` internally.
|
|
15
|
+
- **Fixed**: **Missing `init` Command After Modularization** — restored `kandown init` by adding the initializer module back to the source tree, copying the shipped HTML/config/agent templates, and creating project-root `tasks/` exactly as documented.
|
|
16
|
+
- **Fixed**: **One-Shot Task Commands** — restored the scriptable task command surface that had been partially lost during the split: `kandown list`, `show`, `create`/`new`, `move`, `assign`, `commit`, and `tasks`. JSON output and command-substitution output are clean again because decorative messages are emitted on stderr.
|
|
17
|
+
- **Fixed**: **Daemon Command Surface** — restored `kandown daemon start`, `status`, `restart`, `stop`, `run`, and `refresh-all` handling, including preferred port parsing for explicit daemon runs.
|
|
18
|
+
- **Fixed**: **TUI Command Entrypoints** — restored `kandown board` and `kandown settings`, and made the bundled `bin/tui.js` executable directly so the parent CLI can spawn the terminal interface reliably.
|
|
19
|
+
- **Fixed**: **MCP Stdout Contract** — restored `kandown mcp` dispatch while keeping stdout JSON-only, with initialization and status notices sent to stderr so MCP hosts and shell pipelines can parse responses safely.
|
|
20
|
+
- **Fixed**: **Unsafe Global Symlink Rewrites** — removed the daemon-side behavior that attempted to rewrite global `kandown` symlinks from a bundle-relative path. Package managers now remain the source of truth for the executable, preventing the web daemon from bricking the command.
|
|
21
|
+
- **Fixed**: **Project HTML Refresh Path Resolution** — refreshed `.kandown/kandown.html` from the resolved package root instead of an incorrect `import.meta.url` relative path, ensuring project web bundles are updated from the installed package.
|
|
22
|
+
- **Changed**: **Auto-Updater Global Install Targeting** — hardened the auto-updater to prefer the `npm`/`pnpm` executable living next to the active `kandown` binary. This prevents machines with multiple Node prefixes from updating a different global install than the command the user actually launched.
|
|
23
|
+
- **Added**: **Basic Import Recovery Command** — restored `kandown import <file.json>` for list-shaped JSON and Kandown export-shaped JSON, allowing task files to be recreated from exported data during CLI recovery workflows.
|
|
24
|
+
|
|
3
25
|
## 0.33.2 — 2026-07-21 — "Fix CJS Require Shim & Path Resolution"
|
|
4
26
|
|
|
5
27
|
- **Fixed**: **TUI Require Shim Error (`Dynamic require of "module"`)** — added `createRequire` global banner shim in `tsup.config.ts` so Ink and React CJS dependencies inside `bin/tui.js` execute natively under Node ESM without dynamic require errors.
|