@functional-systems/lambdadb-mcp 0.1.2-dev.9 → 0.1.2

package/CHANGELOG.md

@@ -2,19 +2,21 @@
 
 ## Unreleased
 
+## [0.1.2] - 2026-10-04
+
 - Pin the LambdaDB TypeScript SDK to 0.7.0 and expose all 49 fixed lowercase
   analyzer presets in collection-tool guidance; preserve analyzer serialization.
 - Add optional per-query managed reranking to the MCP schema and SDK request path,
   preserving omission/null, distinct sizes, custom criteria, envelope scores and
   status metadata, including document downloads. Retain SDK validation and errors.
 - Extend local and installed-package contracts for analyzer expansion and reranking;
-  update the opt-in live analyzer check without claiming live feature verification.
+  update the opt-in live analyzer check to cover all 49 names.
 - Add a separate opt-in managed-reranking live suite for real default/custom
   inference, empty candidates, omitted/null behavior and docsUrl envelope
   preservation, with owned-resource cleanup and no fixed relevance expectations.
 - Native SDK usage is unchanged; no Qdrant mapping exists in this server. Supporting
-  backend deployment/model availability remains required. No package is published
-  and existing MCP installations require a separately released update.
+  backend deployment/model availability remains required; existing MCP installations
+  require a version containing these changes.
 
 ## [0.1.1] - 2026-09-29
 

package/README.md

@@ -14,14 +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.
 
-The stable package is available on npm. As verified on 2026-09-29 (KST),
-`latest` resolves to `0.1.1` and `dev` to `0.1.1-dev.7`. Use an exact version for
+The stable package is available on npm. As verified on 2026-10-04 (KST),
+`latest` resolves to `0.1.1` and `dev` to `0.1.2-dev.9`. Use an exact version for
 reproducibility or the default stable channel for initial setup. See
 [release status and policy](RELEASING.md).
 
-[MCP 0.1.1](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.1) is published
-with SDK 0.6.0, keyword facets, match-all queries, and 16 text analyzers. Develop
-starts the next `0.1.2-dev.1` base; check npm for the current published dev version.
+[MCP 0.1.1](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.1) remains the
+published stable release with SDK 0.6.0. Published `0.1.2-dev.9` contains SDK 0.7.0,
+49 fixed text analyzer presets and optional managed reranking. This source prepares
+stable `0.1.2`; it has not yet been published. To preview the published changes,
+use `npx --yes @functional-systems/lambdadb-mcp@0.1.2-dev.9`.
 Existing installations need an MCP version containing these changes; upgrading
 the SDK separately does not update them.
 

package/RELEASING.md

@@ -1,5 +1,30 @@
 # Releasing LambdaDB MCP
 
+## Prepared stable candidate: 0.1.2 (2026-10-04 KST)
+
+[PR #11](https://github.com/lambdadb/lambdadb-mcp/pull/11) merged SDK 0.7.0,
+49 fixed text analyzer presets and optional per-query managed reranking into
+develop at `99896e0279fa7610358e9abafc032dd507b10f40`. The
+[develop workflow](https://github.com/lambdadb/lambdadb-mcp/actions/runs/37189420462)
+completed and published `0.1.2-dev.9`. Registry metadata matches that commit and
+pins SDK 0.7.0; a downloaded tarball was integrity-checked and passed clean
+consumer stdio contracts. As verified on 2026-10-04, `latest` remains `0.1.1`.
+
+`release/0.1.2` prepares stable package/lock versions and a dated changelog for
+review into main. Source, tests, scripts and CI match the merged develop tree.
+Candidate validation is recorded in `docs/validation/2026-10-04-0.1.2.md`.
+Do not treat this preparation as a published stable release. Merge into main with
+a merge commit to retain ancestry, then obtain separate authorization to tag the
+verified main commit as `v0.1.2` and publish its GitHub Release. The release
+workflow tests its exact publication artifact before publishing to `latest`.
+After verification, synchronize main into develop through a PR with the next
+`0.1.3-dev.1` base; do not put stable version metadata on develop.
+
+Both 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. Backend feature/model availability remains required.
+
 ## Current stable release: 0.1.1 (2026-09-29 KST)
 
 [v0.1.1](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.1) tags main
@@ -14,10 +39,9 @@ See `docs/validation/2026-09-29-0.1.1.md` in this source for separate candidate,
 development-service, and published-package evidence. Do not repeat the 0.1.1
 publication or move its tag.
 
-This synchronization brings main back into develop with the next base
-`0.1.2-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.1. Do not merge stable version metadata directly into develop.
+The 0.1.1 synchronization is complete: main was brought back into develop with
+the `0.1.2-dev.1` base through PR #10. Eligible develop merges publish dev versions
+while leaving `latest` on 0.1.1 until an explicitly published stable release.
 Facets need a supporting server and newly built keyword indexes; this release
 does not migrate existing Collections or indexes.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-mcp",
-  "version": "0.1.2-dev.9",
+  "version": "0.1.2",
   "private": false,
   "description": "MCP server for LambdaDB data plane",
   "type": "module",
@@ -61,5 +61,5 @@
     "access": "public",
     "registry": "https://registry.npmjs.org"
   },
-  "gitHead": "99896e0279fa7610358e9abafc032dd507b10f40"
+  "gitHead": "627ffbb3161bc3d41d5f2a5f2a0f5289fd73de3f"
 }