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

package/CHANGELOG.md

@@ -2,6 +2,8 @@
 
 ## 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

package/README.md

@@ -14,18 +14,16 @@ 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-25 (KST), npm `latest` resolves to `0.1.4`. This checkout
-prepares `0.1.5`; it is not yet published. The `dev` channel 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.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.
-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. It replaces the query tool's top-level
@@ -39,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,27 +1,33 @@
 # Releasing LambdaDB MCP
 
-## Prepared stable candidate: 0.1.5 (2026-10-25 KST)
-
-The `release/0.1.5` branch promotes reviewed develop commit
-`bf4536f5a8256a4193e8dcea86f1ecedc626294d`, including
-[Kiro schema PR #25](https://github.com/lambdadb/lambdadb-mcp/pull/25) and
-[dependency PR #26](https://github.com/lambdadb/lambdadb-mcp/pull/26), into main.
-Candidate-only changes are package/lock versions and release documentation;
-application source, tests, dependencies and CI match that reviewed source.
-See the [candidate validation record](docs/validation/2026-10-25-0.1.5.md).
-
-As checked on 2026-10-25 (KST), `latest` remains 0.1.4 and no `v0.1.5` tag
-exists. Candidate validation does not publish a package. After review, merge into
-main while preserving ancestry, then obtain explicit authorization before
-creating the annotated `v0.1.5` tag and publishing its non-prerelease GitHub
-Release. The release workflow must test and publish its exact artifact; verify
-registry identity, integrity, provenance and clean-consumer behavior afterward.
-
-The LambdaDB CLI still pins MCP 0.1.4. Stable CLI users receive this fix only
-after a separate CLI pin update and release. After MCP publication, synchronize
-main back into develop with the next dev base through a PR.
-
-## 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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-mcp",
-  "version": "0.1.5",
+  "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": "1ae40dcbebea734e34ddde024e0991c8bf3fda64"
+  "gitHead": "28ddf4e50e73049f9f824226037e11314f22b8b8"
 }