@functional-systems/lambdadb-mcp 0.1.5-dev.18 → 0.1.6-dev.19

package/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 ## Unreleased
 
+- Synchronize the 0.1.5 release history and start the 0.1.6 development line.
+
+## [0.1.5] - 2026-10-25
+
 - Pin MCP SDK 1.32.2, raise the Zod minimum to 4.6.7, and refresh the affected
   transitive dependencies to clear six npm audit findings. Keep the LambdaDB
   SDK, Node.js floor, tool schemas and read-only defaults unchanged. The new SDK

package/README.md

@@ -14,21 +14,20 @@ MCP server for LambdaDB using the official TypeScript MCP SDK and the official L
 Package: `@functional-systems/lambdadb-mcp`. Executable: `lambdadb-mcp`.
 Requires Node.js >=22.14.0; CI tests the minimum and current Node 22/24 LTS.
 
-As verified on 2026-10-07 (KST), npm `latest` resolves to `0.1.4` and `dev` to
-`0.1.4-dev.15`. Use an exact version for reproducibility or the stable channel for
-initial setup. See [release status and policy](RELEASING.md).
-
-[MCP 0.1.4](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.4) is published
-with LambdaDB SDK `0.8.1`, native embedding and native reranking terminology, and
-MCP SDK `1.31.0`. The MCP SDK update includes a 10 MiB stdio receive-buffer limit
-and revised schema-validation error formatting. Existing tool names, wire fields
-and read-only defaults remain unchanged. This checkout starts the next
-`0.1.5-dev.1` source base; check npm for the current published dev version.
-Existing installations need an MCP release containing these changes; upgrading
-the SDK separately does not update them.
+As verified on 2026-10-25 (KST), npm `latest` resolves to `0.1.5`; `dev` advances
+separately. Use an exact published version for reproducibility or the stable
+channel for initial setup. See [release status and policy](RELEASING.md).
+
+[MCP 0.1.5](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.5) is published
+with LambdaDB SDK `0.8.1`, MCP SDK `1.32.2`, patched dependencies and Kiro/Claude
+query-schema compatibility. This checkout starts the next `0.1.6-dev.1` source
+base; check npm for the current published dev version. Existing direct MCP
+installations need the new MCP version and an agent restart. CLI 0.1.5 still pins
+MCP 0.1.4 and needs a subsequent CLI release with an updated pin.
 
 This checkout pins MCP SDK `1.32.2` and requires Zod `^4.6.7`, with patched
-transitive dependencies in the lockfile. The SDK now treats omitted tool
+transitive dependencies in the lockfile. It replaces the query tool's top-level
+`allOf` with equivalent conditionals for Kiro/Claude compatibility. The SDK now treats omitted tool
 arguments as an empty object; required inputs still fail validation. Its new
 `maxToolInputElements` option remains unset, preserving existing input limits.
 Upstream HTTP redirect/authentication and experimental-task fixes do not add
@@ -38,7 +37,7 @@ those features to this stdio-only server. See the
 ```sh
 npx --yes @functional-systems/lambdadb-mcp
 # Pin the stable release:
-npx --yes @functional-systems/lambdadb-mcp@0.1.4
+npx --yes @functional-systems/lambdadb-mcp@0.1.5
 # Or install globally:
 npm install -g @functional-systems/lambdadb-mcp
 lambdadb-mcp

package/RELEASING.md

@@ -1,6 +1,33 @@
 # Releasing LambdaDB MCP
 
-## Current stable release: 0.1.4 (2026-10-07 KST)
+## Current stable release: 0.1.5 (2026-10-25 KST)
+
+[v0.1.5](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.5) tags main
+commit `1ae40dcbebea734e34ddde024e0991c8bf3fda64`, which merged
+[release PR #27](https://github.com/lambdadb/lambdadb-mcp/pull/27) with preserved
+ancestry. The user explicitly authorized the annotated tag, non-prerelease
+GitHub Release and npm latest publication. The
+[release workflow](https://github.com/lambdadb/lambdadb-mcp/actions/runs/40169478215)
+passed Node.js 22.14.0 / 22 / 24 validation and published its exact tested artifact
+with OIDC and provenance. Registry snapshot: `latest=0.1.5`, `dev=0.1.5-dev.18`.
+
+The downloaded 15-file stable artifact matched the tagged source and registry
+integrity, passed 37 installed-package tests, and had zero consumer audit
+findings. `npm audit signatures` reported no invalid or missing signatures;
+provenance repository, workflow, tag, commit and artifact digest matched.
+Actual Kiro V2/Sonnet called the published MCP directly against a synthetic
+backend without a resolver substitution. A separate actual development-service
+check verified authentication and collection-list access only. No writes or
+search readiness are claimed. See the
+[validation record](docs/validation/2026-10-25-0.1.5.md). Do not repeat publication
+or move the immutable tag.
+
+`release/sync-0.1.5` brings this main history back into develop with the next
+`0.1.6-dev.1` source base. Merge with preserved ancestry. Eligible develop merges
+can publish dev versions while latest stays on 0.1.5. CLI 0.1.5 still pins MCP
+0.1.4; its separate pin update/release is required for stable CLI users.
+
+## Previous stable release: 0.1.4 (2026-10-07 KST)
 
 [v0.1.4](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.4) tags main
 commit `f84038962bbdc6f5375b873727d0cf54d843c7b2`, which merged
@@ -20,8 +47,9 @@ matched the release source and artifact. No new paid/state-changing live smoke
 was run. See [validation evidence](docs/validation/2026-10-07-0.1.4.md).
 Do not repeat publication or move the tag.
 
-`release/sync-0.1.4` brings main back into develop with the next source base
-`0.1.5-dev.1`. Review it into develop using a merge commit to preserve ancestry.
+The 0.1.4 synchronization completed in
+[PR #22](https://github.com/lambdadb/lambdadb-mcp/pull/22), bringing main back into
+develop with the next source base `0.1.5-dev.1` and preserved ancestry.
 Eligible develop merges can publish new dev versions while `latest` stays on
 0.1.4. Do not merge stable version metadata directly into develop.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-mcp",
-  "version": "0.1.5-dev.18",
+  "version": "0.1.6-dev.19",
   "private": false,
   "description": "MCP server for LambdaDB data plane",
   "type": "module",
@@ -62,5 +62,5 @@
     "access": "public",
     "registry": "https://registry.npmjs.org"
   },
-  "gitHead": "bf4536f5a8256a4193e8dcea86f1ecedc626294d"
+  "gitHead": "28ddf4e50e73049f9f824226037e11314f22b8b8"
 }