@functional-systems/lambdadb-mcp 0.1.0-dev.5 → 0.1.0

package/CHANGELOG.md

@@ -1,11 +1,12 @@
 # Changelog
 
-## Unreleased
+## [0.1.0] - 2026-09-20
 
-- Prepare `@functional-systems/lambdadb-mcp` and the `lambdadb-mcp` executable for npm/npx distribution under Apache-2.0.
-- Add gated OIDC publishing for develop, rc and stable channels with exact tarball consumer checks.
+- Package `@functional-systems/lambdadb-mcp` and the `lambdadb-mcp` executable for npm/npx distribution under Apache-2.0.
+- Add OIDC publishing for develop, rc and stable channels with exact tarball consumer checks; automatic dev publishing is enabled.
 - Derive the MCP server version from package metadata and close the process on stdio disconnect or termination.
 - Raise the supported Node.js floor to 22.14.0; verify the minimum and current Node 22/24 LTS.
 - Preserve the existing environment variables, read-only default and explicit write opt-in.
 - Require explicit development-project confirmation before running the optional live smoke.
 - Refresh compatible locked dependencies; the audited dependency tree has no known advisories at validation time.
+- Record successful npm-installed stdio and authorized development-service validation of the dev distribution.

package/README.md

@@ -16,7 +16,7 @@ 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.4`; `latest` still points to the bootstrap prerelease
+`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
 [release status and policy](RELEASING.md).
 

package/RELEASING.md

@@ -13,11 +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.4`; `latest=0.1.0-dev.1` is still the bootstrap prerelease.
+- `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.
-- main still needs the publishing workflow and reviewed release metadata before
-  rc/stable publication. See [explicit rc/stable publication](#explicit-rcstable-publication).
+- 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).
 - 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-dev.5",
+  "version": "0.1.0",
   "private": false,
   "description": "MCP server for LambdaDB data plane",
   "type": "module",
@@ -60,5 +60,5 @@
     "access": "public",
     "registry": "https://registry.npmjs.org"
   },
-  "gitHead": "f6a58dcdcd56590137d3a36fc588d0e13fa7f6cb"
+  "gitHead": "29be7b9cca26c6e619e9f9ad689cca3663c09d46"
 }