@functional-systems/lambdadb-mcp 0.1.0 → 0.1.1-dev.6

package/CHANGELOG.md

@@ -1,5 +1,7 @@
 # Changelog
 
+## Unreleased
+
 ## [0.1.0] - 2026-09-20
 
 - Package `@functional-systems/lambdadb-mcp` and the `lambdadb-mcp` executable for npm/npx distribution under Apache-2.0.

package/README.md

@@ -14,19 +14,20 @@ 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 package is published on the `dev` channel. Until a stable release exists,
-select `@dev` or an exact published prerelease. As verified on 2026-09-20 (KST),
-`dev` resolves to `0.1.0-dev.5`; `latest` still points to the bootstrap prerelease
-`0.1.0-dev.1` and does not indicate a stable release. See
+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
+reproducibility or the default stable channel for initial setup. See
 [release status and policy](RELEASING.md).
 
 ```sh
-npx --yes @functional-systems/lambdadb-mcp@dev
-# After a stable release exists:
+npx --yes @functional-systems/lambdadb-mcp
+# Pin the first stable release:
+npx --yes @functional-systems/lambdadb-mcp@0.1.0
+# Or install globally:
 npm install -g @functional-systems/lambdadb-mcp
 lambdadb-mcp
-# Or run without a global installation:
-npx --yes @functional-systems/lambdadb-mcp
+# Opt into development builds explicitly:
+npx --yes @functional-systems/lambdadb-mcp@dev
 ```
 
 Set the environment variables below in your MCP client or securely in the parent

package/RELEASING.md

@@ -13,13 +13,13 @@ As verified on **2026-09-20 (KST)**:
 - Automatic dev publication is enabled (`NPM_DEV_PUBLISH_ENABLED=true`). Eligible
   develop pushes publish after validation; a documentation-only merge can also
   produce a new dev version.
-- `dev=0.1.0-dev.5`; `latest=0.1.0-dev.1` is still the bootstrap prerelease.
-  There is no rc/stable release or GitHub Release yet. Prefer `@dev` or an exact
-  published version until stable is available.
-- The `0.1.0` stable candidate carries the publishing workflow and matching dated
-  release metadata for main review. Merging the candidate validates main but does
-  not publish a package. Publication requires the explicit GitHub release
-  `v0.1.0` with `prerelease: false`, which publishes to `latest`; see [explicit rc/stable publication](#explicit-rcstable-publication).
+- First stable release: [`v0.1.0`](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.0).
+  The [release workflow](https://github.com/lambdadb/lambdadb-mcp/actions/runs/35494365745)
+  published `0.1.0` with OIDC and provenance; `latest=0.1.0`, `dev=0.1.0-dev.5`.
+- main contains the stable release and publishing workflow. develop resumes with
+  the `0.1.1-dev.1` base; CI generates its dev counter from first-parent history.
+  Eligible develop pushes can publish the next dev version while leaving
+  `latest` on `0.1.0`.
 - See the [validation record](https://github.com/lambdadb/lambdadb-mcp/blob/develop/docs/validation/2026-09-20-npm.md) for package,
   provenance, and live-service evidence and their separate scopes.
 

package/package.json

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