LumabyteCo/clarifyprompt-mcp

What's new in 1.6.7

Hot-fix for the `CI / docker build` failure on 1.6.6. No engine code, MCP tool surface, platform, or env-var changes.

Root cause

`[email protected]` (released 2026-05) explicitly removed prebuilt binaries for Node.js v20 and v23 because Node 20 reached EOL in April 2026. My 1.6.6 lockfile regeneration happened to pull 12.10.0 within the `^12.9.0` caret. Without a prebuilt, `npm ci` in the `node:20-slim` Docker image fell through to `node-gyp rebuild`, which needs Python + a C++ toolchain — neither present in the slim base.

Fix

Bumped `Dockerfile` base from `node:20-slim` to `node:22-slim` — Node 22 is the current active LTS line, where `better-sqlite3` still ships prebuilts. One-line change in two FROM directives.

Why bump the base, not pin the dep?

Node 20 is genuinely EOL and the ecosystem is moving on. Pinning `better-sqlite3` to `12.9.0` would defer the same break as soon as the next version of any other native dep drops Node 20 too. Honest fix: follow the ecosystem.

Verified locally

• `docker build -t clarifyprompt-mcp:ci-test .`: clean
• `docker run ... node -e 'require("better-sqlite3"); require("sqlite-vec")'`: both native deps load
• All 5 `sqlite-vec` platform binaries still in `package-lock.json` (1.6.6 fix held)
• `npm audit --production`: 0 vulnerabilities (unchanged)

What's unchanged

• The non-Docker CI matrix (Node 18 / 20 / 22 across macOS + Ubuntu) still runs because regular runners can compile-from-source as fallback. Whether to prune EOL Node versions from that matrix is a separate decision; 1.6.7 doesn't touch it.
• Engine code, MCP tools (still 23), platforms (still 60+), env vars (unchanged).

Install

```bash
npm install -g [email protected]
```