@functional-systems/lambdadb-mcp 0.1.4-dev.15 → 0.1.4

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 ## Unreleased
 
+## [0.1.4] - 2026-10-07
+
+- Standardize feature guidance as native embedding and native reranking; pin the
+  LambdaDB TypeScript SDK to 0.8.1. Preserve public identifiers, legacy wire fields,
+  application error strings, existing behavior tests and pinned source links.
+- Update the MCP SDK to 1.31.0 for GHSA-6qxp-vccf-f47h. The advisory concerns HTTP
+  OAuth clients; this stdio server does not use the affected OAuth path.
+- Document upstream compatibility differences: the MCP SDK limits the stdio receive
+  buffer to 10 MiB and closes the transport on overflow, and formats schema
+  validation errors with field paths. Application tool names, schemas and defaults
+  remain unchanged.
+
 ## [0.1.3] - 2026-10-06
 
 - Pin the stable LambdaDB SDK to 0.8.0; expose Bayesian candidate budgets and

package/README.md

@@ -14,19 +14,19 @@ 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.
 
-The stable package is available on npm. As verified on 2026-10-06 (KST),
-`latest` resolves to `0.1.3` and `dev` to `0.1.3-dev.11`. Use an exact version for
-reproducibility or the default stable channel for initial setup. See
-[release status and policy](RELEASING.md).
-
-[MCP 0.1.3](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.3) is the
-published stable release with SDK 0.8.0, Bayesian hybrid search and native
-embedding configuration, alongside native reranking and all 49 text analyzers.
-This synchronization starts the next `0.1.4-dev.1` source base; check npm for the
-current published dev version. Use exact stable version `0.1.3` for reproducible
-installed execution.
-Existing installations need an MCP version containing these changes; upgrading
-the SDK separately does not update them.
+As verified on 2026-10-07 (KST), npm `latest` resolves to `0.1.3` and `dev` to
+`0.1.4-dev.15`. Use an exact version for reproducibility. Check the registry before
+installing a newly prepared release; source metadata alone does not establish npm
+publication. See [release status and policy](RELEASING.md).
+
+This checkout prepares MCP `0.1.4` 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.
+[MCP 0.1.3](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.3) remains the
+verified stable installation in the snapshot above. Existing installations need
+an MCP release containing these changes; upgrading the SDK separately does not
+update them.
 
 ```sh
 npx --yes @functional-systems/lambdadb-mcp

package/RELEASING.md

@@ -1,5 +1,27 @@
 # Releasing LambdaDB MCP
 
+## Stable candidate: 0.1.4 (2026-10-07 KST)
+
+`release/0.1.4` promotes reviewed develop commit
+`752fd825480556305f2a89025a0d87f5126b4d1b` to main with stable package/lock metadata
+and dated release notes. LambdaDB SDK 0.8.1 standardizes native embedding and
+native reranking terminology. MCP SDK 1.31.0 removes the reported OAuth-client
+advisory; its stdio receive-buffer limit is 10 MiB and schema-validation error
+formatting includes field paths. Existing application tool contracts remain.
+
+The user authorized the stable release. Complete main PR CI and review, retain
+ancestry with a merge commit, tag the verified main commit `v0.1.4`, and publish
+the GitHub Release to trigger the existing OIDC workflow. Main pushes validate
+only. Do not publish manually or treat this candidate as already on npm.
+
+Registry snapshot: `latest=0.1.3`, `dev=0.1.4-dev.15`. The published dev package
+matches the reviewed commit and both SDK pins, passed 35 installed-package tests,
+and has matching registry integrity and provenance statement metadata. See
+[the validation record](docs/validation/2026-10-07-0.1.4.md) for distinct candidate
+and published-package evidence. No new paid or state-changing live smoke is
+included. After publication verification, synchronize main into develop through
+a PR with the next `0.1.5-dev.1` base; that merge can publish a new dev version.
+
 ## Current stable release: 0.1.3 (2026-10-06 KST)
 
 [v0.1.3](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.3) tags main

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-mcp",
-  "version": "0.1.4-dev.15",
+  "version": "0.1.4",
   "private": false,
   "description": "MCP server for LambdaDB data plane",
   "type": "module",
@@ -62,5 +62,5 @@
     "access": "public",
     "registry": "https://registry.npmjs.org"
   },
-  "gitHead": "752fd825480556305f2a89025a0d87f5126b4d1b"
+  "gitHead": "f84038962bbdc6f5375b873727d0cf54d843c7b2"
 }