@functional-systems/lambdadb-mcp 0.1.3-dev.11 → 0.1.4-dev.12

package/CHANGELOG.md

@@ -2,6 +2,8 @@
 
 ## Unreleased
 
+## [0.1.3] - 2026-10-06
+
 - Pin the stable LambdaDB SDK to 0.8.0; expose Bayesian candidate budgets and
   native embedding configuration in MCP guidance while preserving free-form
   queries, SDK/server validation, rerank defaults, errors and response metadata.

package/README.md

@@ -14,23 +14,24 @@ 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-04 (KST),
-`latest` resolves to `0.1.2` and `dev` to `0.1.2-dev.9`. Use an exact version for
+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.2](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.2) is the
-published stable release with SDK 0.7.0, 49 fixed text analyzer presets and optional
-managed reranking. This synchronization starts the next `0.1.3-dev.1` source base;
-check npm for the current published dev version. Use the exact stable version
-`0.1.2` for reproducible installed execution.
+[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 managed 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.
 
 ```sh
 npx --yes @functional-systems/lambdadb-mcp
 # Pin the stable release:
-npx --yes @functional-systems/lambdadb-mcp@0.1.2
+npx --yes @functional-systems/lambdadb-mcp@0.1.3
 # Or install globally:
 npm install -g @functional-systems/lambdadb-mcp
 lambdadb-mcp

package/RELEASING.md

@@ -1,6 +1,28 @@
 # Releasing LambdaDB MCP
 
-## Current stable release: 0.1.2 (2026-10-04 KST)
+## 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
+commit `159b84aace7d9352cf8e5315bc7f7192e8d65a41`, which merged
+[release PR #15](https://github.com/lambdadb/lambdadb-mcp/pull/15) using an
+explicitly authorized admin merge commit and preserved ancestry. The
+[release workflow](https://github.com/lambdadb/lambdadb-mcp/actions/runs/37458444410)
+passed Node 22.14.0 / 22 / 24 validation and published its exact tested artifact
+with OIDC and provenance. Registry snapshot: `latest=0.1.3`, `dev=0.1.3-dev.11`.
+
+SDK 0.8.0 adds Bayesian candidate budgets and native embedding configuration.
+Existing tool names, free-form inputs, rerank defaults and metadata, SDK downloads,
+and read-only defaults remain. Older servers still require
+`managedEmbedding: true`; Bayesian/native inputs require a supporting deployment.
+See `docs/validation/2026-10-06-0.1.3.md` for separate candidate, source-build live,
+and published-package evidence. Do not repeat publication or move the tag.
+
+`release/sync-0.1.3` brings main back into develop with the next source base
+`0.1.4-dev.1`. Review it into develop using a merge commit to preserve ancestry.
+Eligible develop merges may publish new dev versions while `latest` stays on
+0.1.3. Do not merge stable version metadata directly into develop.
+
+## Previous stable release: 0.1.2 (2026-10-04 KST)
 
 [v0.1.2](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.2) tags main
 commit `627ffbb3161bc3d41d5f2a5f2a0f5289fd73de3f`, which merged
@@ -18,12 +40,12 @@ reranking. Read-only defaults and explicit write opt-in remain. See
 source-build live, published dev and published stable evidence. Do not repeat the
 0.1.2 publication or move its tag.
 
-This synchronization brings main back into develop with the next base
-`0.1.3-dev.1`. Review it into develop using a merge commit to preserve ancestry.
-Eligible develop merges may publish a new dev version while `latest` stays on
-0.1.2. Do not merge stable version metadata directly into develop.
+The 0.1.2 synchronization is complete: PR #13 brought main back into develop
+with the `0.1.3-dev.1` base. Eligible develop merges may publish new dev versions
+while `latest` stays on 0.1.2 until an explicitly authorized stable release.
+Do not merge stable version metadata directly into develop.
 
-Both live suites require explicit designation of a development project. Reranking
+Live suites require explicit designation of a development project. Reranking
 also requires managed inference opt-in; no Jev API key is required. Live contract
 checks do not establish production deployment, search quality, load/failure
 coverage or billing readiness. Supporting backend deployment/model availability

package/package.json

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