@functional-systems/lambdadb-mcp 0.1.1-dev.7 → 0.1.1

package/CHANGELOG.md

@@ -2,6 +2,8 @@
 
 ## Unreleased
 
+## [0.1.1] - 2026-09-29
+
 - Pin the LambdaDB TypeScript SDK to 0.6.0, including all 16 text analyzers.
 - Add keyword facets, query omission for match-all, and facet-only `size: 0` to
   `lambdadb_query_collection`. Preserve omitted/null bucket sizes and facet results,

package/README.md

@@ -14,11 +14,17 @@ 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-20 (KST),
-`latest` resolves to `0.1.0` and `dev` to `0.1.0-dev.5`. Use an exact version for
+The stable package is available on npm. As verified on 2026-09-29 (KST),
+`latest` resolves to `0.1.0` and `dev` to `0.1.1-dev.7`. Use an exact version for
 reproducibility or the default stable channel for initial setup. See
 [release status and policy](RELEASING.md).
 
+This source targets MCP **0.1.1**, with SDK 0.6.0, keyword facets, match-all queries,
+and 16 text analyzers. Check [GitHub Releases](https://github.com/lambdadb/lambdadb-mcp/releases)
+and npm for publication status; source version metadata alone is not evidence of publication.
+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 first stable release:

package/RELEASING.md

@@ -1,5 +1,26 @@
 # Releasing LambdaDB MCP
 
+## Prepared stable candidate: 0.1.1 (2026-09-29 KST)
+
+The `release/0.1.1` branch promotes reviewed develop commit
+`d1a041ed8497eb8113b616faf87b2702fb5b80c5` with matching package/lock versions and
+a dated changelog. SDK 0.6.0 adds keyword facets, match-all and facet-only queries,
+and all 16 text analyzers. Read-only defaults and explicit write opt-in remain.
+See `docs/validation/2026-09-29-0.1.1.md` in the reviewed release source for the
+candidate validation record.
+
+Review the release PR into **main using a merge commit** to preserve ancestry.
+Preparation does not publish 0.1.1. After the main candidate is verified and
+publication is authorized, tag that main commit `v0.1.1` and publish a non-prerelease
+GitHub Release. The existing workflow validates, packs, tests, and publishes its
+exact tarball to npm `latest` with OIDC. Verify version, gitHead, integrity,
+provenance, and installed behavior before announcing availability.
+
+After publication, synchronize main back into develop through a PR with the next
+base `0.1.2-dev.1`. Do not merge stable version metadata directly into develop.
+Facets need a supporting server and newly built keyword indexes; this release
+does not migrate existing Collections or indexes.
+
 ## Status and policy
 
 As verified on **2026-09-20 (KST)**:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-mcp",
-  "version": "0.1.1-dev.7",
+  "version": "0.1.1",
   "private": false,
   "description": "MCP server for LambdaDB data plane",
   "type": "module",
@@ -60,5 +60,5 @@
     "access": "public",
     "registry": "https://registry.npmjs.org"
   },
-  "gitHead": "d1a041ed8497eb8113b616faf87b2702fb5b80c5"
+  "gitHead": "40a8afc25bb93fb14d03d23e3ab38aa1924cf060"
 }