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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +5 -2
  2. package/README.md +9 -8
  3. package/RELEASING.md +7 -5
  4. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -2,10 +2,13 @@
2
2
 
3
3
  ## Unreleased
4
4
 
5
- - Prepare `@functional-systems/lambdadb-mcp` and the `lambdadb-mcp` executable for npm/npx distribution under Apache-2.0.
6
- - Add gated OIDC publishing for develop, rc and stable channels with exact tarball consumer checks.
5
+ ## [0.1.0] - 2026-09-20
6
+
7
+ - Package `@functional-systems/lambdadb-mcp` and the `lambdadb-mcp` executable for npm/npx distribution under Apache-2.0.
8
+ - Add OIDC publishing for develop, rc and stable channels with exact tarball consumer checks; automatic dev publishing is enabled.
7
9
  - Derive the MCP server version from package metadata and close the process on stdio disconnect or termination.
8
10
  - Raise the supported Node.js floor to 22.14.0; verify the minimum and current Node 22/24 LTS.
9
11
  - Preserve the existing environment variables, read-only default and explicit write opt-in.
10
12
  - Require explicit development-project confirmation before running the optional live smoke.
11
13
  - Refresh compatible locked dependencies; the audited dependency tree has no known advisories at validation time.
14
+ - Record successful npm-installed stdio and authorized development-service validation of the dev distribution.
package/README.md CHANGED
@@ -14,19 +14,20 @@ MCP server for LambdaDB using the official TypeScript MCP SDK and the official L
14
14
  Package: `@functional-systems/lambdadb-mcp`. Executable: `lambdadb-mcp`.
15
15
  Requires Node.js >=22.14.0; CI tests the minimum and current Node 22/24 LTS.
16
16
 
17
- The package is published on the `dev` channel. Until a stable release exists,
18
- select `@dev` or an exact published prerelease. As verified on 2026-09-20 (KST),
19
- `dev` resolves to `0.1.0-dev.4`; `latest` still points to the bootstrap prerelease
20
- `0.1.0-dev.1` and does not indicate a stable release. See
17
+ The stable package is available on npm. As verified on 2026-09-20 (KST),
18
+ `latest` resolves to `0.1.0` and `dev` to `0.1.0-dev.5`. Use an exact version for
19
+ reproducibility or the default stable channel for initial setup. See
21
20
  [release status and policy](RELEASING.md).
22
21
 
23
22
  ```sh
24
- npx --yes @functional-systems/lambdadb-mcp@dev
25
- # After a stable release exists:
23
+ npx --yes @functional-systems/lambdadb-mcp
24
+ # Pin the first stable release:
25
+ npx --yes @functional-systems/lambdadb-mcp@0.1.0
26
+ # Or install globally:
26
27
  npm install -g @functional-systems/lambdadb-mcp
27
28
  lambdadb-mcp
28
- # Or run without a global installation:
29
- npx --yes @functional-systems/lambdadb-mcp
29
+ # Opt into development builds explicitly:
30
+ npx --yes @functional-systems/lambdadb-mcp@dev
30
31
  ```
31
32
 
32
33
  Set the environment variables below in your MCP client or securely in the parent
package/RELEASING.md CHANGED
@@ -13,11 +13,13 @@ As verified on **2026-09-20 (KST)**:
13
13
  - Automatic dev publication is enabled (`NPM_DEV_PUBLISH_ENABLED=true`). Eligible
14
14
  develop pushes publish after validation; a documentation-only merge can also
15
15
  produce a new dev version.
16
- - `dev=0.1.0-dev.4`; `latest=0.1.0-dev.1` is still the bootstrap prerelease.
17
- There is no rc/stable release or GitHub Release yet. Prefer `@dev` or an exact
18
- published version until stable is available.
19
- - main still needs the publishing workflow and reviewed release metadata before
20
- rc/stable publication. See [explicit rc/stable publication](#explicit-rcstable-publication).
16
+ - First stable release: [`v0.1.0`](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.0).
17
+ The [release workflow](https://github.com/lambdadb/lambdadb-mcp/actions/runs/35494365745)
18
+ published `0.1.0` with OIDC and provenance; `latest=0.1.0`, `dev=0.1.0-dev.5`.
19
+ - main contains the stable release and publishing workflow. develop resumes with
20
+ the `0.1.1-dev.1` base; CI generates its dev counter from first-parent history.
21
+ Eligible develop pushes can publish the next dev version while leaving
22
+ `latest` on `0.1.0`.
21
23
  - See the [validation record](https://github.com/lambdadb/lambdadb-mcp/blob/develop/docs/validation/2026-09-20-npm.md) for package,
22
24
  provenance, and live-service evidence and their separate scopes.
23
25
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@functional-systems/lambdadb-mcp",
3
- "version": "0.1.0-dev.5",
3
+ "version": "0.1.1-dev.6",
4
4
  "private": false,
5
5
  "description": "MCP server for LambdaDB data plane",
6
6
  "type": "module",
@@ -60,5 +60,5 @@
60
60
  "access": "public",
61
61
  "registry": "https://registry.npmjs.org"
62
62
  },
63
- "gitHead": "f6a58dcdcd56590137d3a36fc588d0e13fa7f6cb"
63
+ "gitHead": "fc5765bec9dd84f239840eab734531a945d8a70c"
64
64
  }