@functional-systems/lambdadb-cli 0.1.2 → 0.1.3-dev.13

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## [Unreleased]
 
+### Maintenance
+
+- Synchronize the 0.1.2 release history and start the 0.1.3 development line.
+- Prepare the Homebrew formula for verified stable 0.1.2 and record npm publication evidence.
+
 ## [0.1.2] - 2026-10-04
 
 ### Fixed

package/README.md

@@ -19,7 +19,7 @@ lambdadb --help
 ```
 
 For reproducible CI runs, pin an exact published version such as
-`@functional-systems/lambdadb-cli@0.1.1`. To try development builds, explicitly use
+`@functional-systems/lambdadb-cli@0.1.2`. To try development builds, explicitly use
 `@functional-systems/lambdadb-cli@dev`; this moving channel contains prereleases.
 Installed CLIs do not update themselves. See
 [RELEASING.md](RELEASING.md#current-status) for release status and

package/RELEASING.md

@@ -2,19 +2,25 @@
 
 ## Current status
 
-CLI 0.1.2 is ready for release review from reviewed develop commit `aef74a3` (PR #14).
-The candidate pins SDK 0.7.0, supports 49 fixed text analyzer presets and optional
-per-query managed reranking, and preserves fixed rerank metadata during credential
-redaction. The published 0.1.2-dev.12 artifact passed independent consumer,
-provenance/signature and authorized development-service checks. The separately
-installed 0.1.2 candidate also passed the expanded live smoke; its earlier failed
-attempt and independent cleanup are recorded in [VALIDATION.md](VALIDATION.md).
-
-Stable 0.1.2 is not published yet. The release PR targets main; its merge, immutable
-`v0.1.2` tag and GitHub Release remain separate approved actions. After publishing,
-verify npm latest, artifact integrity/provenance and clean consumers before updating
-Homebrew. Keep develop on its dev version while this release branch is reviewed;
-synchronize main back with the next `0.1.3-dev.1` base after release.
+CLI 0.1.2 was published on 2026-10-04 from merged main commit
+`6628fe0ed1f405c88fbd91d591e5223d3250dd73` through
+[GitHub Release v0.1.2](https://github.com/lambdadb/lambdadb-cli/releases/tag/v0.1.2)
+and the [successful OIDC workflow](https://github.com/lambdadb/lambdadb-cli/actions/runs/37191188846).
+It pins SDK 0.7.0 and includes 49 fixed analyzer presets, optional per-query
+managed reranking and credential-safe fixed rerank metadata.
+
+Independent registry verification confirmed latest=0.1.2 and dev=0.1.2-dev.12.
+The published tarball is byte-identical to the reviewed, live-tested candidate.
+A clean registry consumer passed all 46 CLI contracts, version/help, SDK version,
+integrity, four registry signatures and three attestations. Decoded provenance
+identifies the release commit, tag and workflow. See
+[publication evidence](VALIDATION.md#cli-012-publication-2026-10-04).
+
+This post-release branch synchronizes main into develop with 0.1.3-dev.1 and
+prepares the verified 0.1.2 Homebrew formula. The public tap still provides 0.1.1
+until its separate formula PR is reviewed and merged. Publication and bounded
+development smoke do not establish production deployment, search quality,
+load/failure coverage or billing readiness.
 
 ## CLI 0.1.1 publication
 

package/VALIDATION.md

@@ -3,6 +3,38 @@
 Updated: 2026-10-04. Local contract tests use loopback servers and synthetic
 credentials. Authenticated development-project evidence is recorded separately.
 
+## CLI 0.1.2 publication (2026-10-04)
+
+[PR #15](https://github.com/lambdadb/lambdadb-cli/pull/15) merged as
+`6628fe0ed1f405c88fbd91d591e5223d3250dd73`. The annotated v0.1.2 tag points to
+that commit. [GitHub Release v0.1.2](https://github.com/lambdadb/lambdadb-cli/releases/tag/v0.1.2)
+triggered [OIDC publication](https://github.com/lambdadb/lambdadb-cli/actions/runs/37191188846),
+which passed Node 22/24 validation and exact-artifact tests on attempt 1.
+
+- Registry latest=0.1.2; dev=0.1.2-dev.12 remained unchanged.
+- Downloaded npm tarball is byte-identical to the reviewed final candidate and
+  merged-main pack. SHA-256:
+  `e63c2c0fd624e1d81c45c5ba24d641a11ee0ecdc60f063aba4268e06547761ea`.
+  Registry SHA-512 integrity:
+  `sha512-9l1WPN2vrX+JXRjuOh7Uz5DCVcaiV/YLpYKgZb7ORU1jphaAIx38VSWeiQitz0V2Nw/b1vTxfcXzvra6EAkaFg==`.
+- An isolated registry consumer passed all 46 installed CLI contracts and
+  version/help. Its lockfile integrity matched npm and SDK resolves to 0.7.0.
+  npm audit signatures verified four registry signatures and three attestations.
+- Decoded [provenance](https://registry.npmjs.org/-/npm/v1/attestations/@functional-systems%2flambdadb-cli@0.1.2)
+  matched the artifact digest, repository, release commit, refs/tags/v0.1.2,
+  publish.yaml and workflow run 37191188846. Verification retried registry reads
+  during propagation without another publication. Temporary consumer, archive
+  and cache were removed.
+- The candidate live evidence below applies to the identical published artifact;
+  no additional live run was performed. The earlier failed sample remains recorded.
+- Formula handoff pins this npm tarball and release lockfile SHA-256
+  `e2d12af262d13c3a23073d1313b183766bb40b5360abeb0d773b5100819dac65`.
+  Public-tap installation and upgrade remain pending its separate PR merge.
+
+These checks establish artifact publication and the recorded development sample;
+production deployment, search quality, load/failure coverage and billing readiness
+remain separate dependencies.
+
 ## CLI 0.1.2 stable candidate (2026-10-04)
 
 Prepared release/0.1.2 from reviewed develop merge `aef74a3`, retaining SDK 0.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-cli",
-  "version": "0.1.2",
+  "version": "0.1.3-dev.13",
   "private": false,
   "description": "Project-scoped LambdaDB command-line tools",
   "type": "module",
@@ -52,5 +52,6 @@
   "bugs": {
     "url": "https://github.com/lambdadb/lambdadb-cli/issues"
   },
-  "license": "Apache-2.0"
+  "license": "Apache-2.0",
+  "gitHead": "aefbaeed9c799e76dd7a9501ecda6ab80dc6e958"
 }