Releases: lambdadb/lambdadb-cli
Release list
LambdaDB CLI 0.1.0
First stable release of the project-scoped LambdaDB CLI for developers, coding agents and CI.
Included
- Configure connections and diagnose project/API access with
configureanddoctor. - List, describe and create collections from JSON index settings.
- Import JSONL documents through ordinary or bulk SDK writes and fetch documents by ID.
- Execute JSON query requests with explicit project, collection and branch/tag/alias read targets.
- Stable JSON envelopes, documented exit codes, bounded requests and distinct accepted, rejected, partial and unknown write outcomes.
- LambdaDB TypeScript SDK 0.5.1, Node.js 22.14+, Apache-2.0 license.
Install
Available now on npm:
npm install --global @functional-systems/lambdadb-cli@0.1.0
lambdadb --version
lambdadb --helpThe stable npm channel is latest; development builds remain on dev.
Verification
Release commit: c8d389f3264d641ae6eafc7737fedd5ea046ddf1. Its Git tree exactly matches the reviewed candidate 658ea7ccdce535bbd4f2e29ae06813e2f2e716e2 from promotion PR #5.
- Clean local install, lint, types, all 59 source tests and 35 installed-package contracts passed.
- Main CI passed Node 22 and 24 validation.
- Installed-candidate live smoke passed against the explicitly designated development project: connection, collection creation, two ordinary documents with 3 MiB payloads each, one bulk document, and exact committed query/fetch contents on
branch:mainin approximately 69 seconds. - Temporary collection cleanup was independently confirmed. No credentials were committed or supplied to CI.
This bounded sample does not establish general readiness or production performance. Live tag/alias and the service's selection of offloaded responses were not proven; their request forwarding and SDK download handling have local contract coverage. Accepted writes are not reported as immediately searchable. Code-search ingestion/embedding, Console administration and durable import resume are outside this release.
See the validation record, changelog and usage guide.
Publication verified
The OIDC release workflow succeeded on attempt 1. Registry checks confirmed latest=0.1.0 and preserved dev=0.1.0-dev.5. A clean unqualified npm installation resolved to 0.1.0 and passed version/help plus all 35 CLI contract tests. Tarball integrity, installed lockfile and provenance subject matched. npm signature verification passed; provenance identifies the release commit, refs/tags/v0.1.0 and workflow attempt 1. Version/tag and attestation metadata propagated separately; verification used read retries without republishing.