@functional-systems/lambdadb-mcp 0.1.1 → 0.1.2-dev.8

package/README.md

@@ -15,20 +15,20 @@ 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.0` and `dev` to `0.1.1-dev.7`. Use an exact version for
+`latest` resolves to `0.1.1` 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.
+[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.
 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:
-npx --yes @functional-systems/lambdadb-mcp@0.1.0
+# Pin the stable release:
+npx --yes @functional-systems/lambdadb-mcp@0.1.1
 # Or install globally:
 npm install -g @functional-systems/lambdadb-mcp
 lambdadb-mcp

package/RELEASING.md

@@ -1,27 +1,27 @@
 # 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.
+## 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
+commit `40a8afc25bb93fb14d03d23e3ab38aa1924cf060`, which merged the reviewed release
+PR with preserved ancestry. The [release workflow](https://github.com/lambdadb/lambdadb-mcp/actions/runs/36557646939)
+passed Node 22.14.0 / 22 / 24 validation and published the tested artifact with
+OIDC and provenance. Registry snapshot: `latest=0.1.1`, `dev=0.1.1-dev.7`.
+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 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.
 Facets need a supporting server and newly built keyword indexes; this release
 does not migrate existing Collections or indexes.
 
-## Status and policy
+## Historical bootstrap and 0.1.0 status
 
 As verified on **2026-09-20 (KST)**:
 

package/package.json

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