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

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,34 @@
 
 ## 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.
+
+At stable publication, 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).
+
+[PR #16](https://github.com/lambdadb/lambdadb-cli/pull/16) synchronized main into
+develop with the 0.1.3-dev.1 base. Its successful automatic publication produced
+0.1.3-dev.13; an independent registry consumer passed all 46 CLI contracts,
+integrity, signature and provenance checks. At verification, dev=0.1.3-dev.13
+and latest=0.1.2.
+
+[Homebrew PR #6](https://github.com/lambdadb/homebrew-tap/pull/6) merged the matching
+0.1.2 formula. Public-tap installation passed on macOS arm64 and Linux x86_64.
+A separate disposable-tap macOS arm64 upgrade from 0.1.1 to 0.1.2 also passed;
+existing-user public-tap upgrades and Linux upgrades were not tested. See
+[post-release evidence](VALIDATION.md#cli-012-post-release-verification-2026-10-04).
+Publication and bounded development smoke do not establish production deployment,
+search quality, load/failure coverage or billing readiness.
 
 ## CLI 0.1.1 publication
 
@@ -31,10 +46,11 @@ A clean unqualified npm installation selected CLI 0.1.1 and SDK 0.6.0, passed al
 tarball is byte-identical to the tested final candidate; provenance identifies the
 release commit, tag and workflow. See [VALIDATION.md](VALIDATION.md#cli-011-publication).
 
-The post-release branch synchronizes main history into develop with `0.1.2-dev.1`
-and prepares the 0.1.1 Homebrew formula. The public tap was checked on 2026-10-04
-and matches that verified 0.1.1 formula; the 0.1.2 handoff follows publication. Facets still require a supporting server and newly built keyword
-indexes; publication does not migrate Collections or upgrade installed CLIs.
+The 0.1.1 post-release synchronization started the `0.1.2-dev.1` development base
+and prepared the 0.1.1 Homebrew formula. The public tap matched that formula at
+the pre-release check on 2026-10-04; the completed 0.1.2 handoff is recorded above.
+Facets still require a supporting server and newly built keyword indexes;
+publication does not migrate Collections or upgrade installed CLIs.
 
 ## Prior publication status
 
@@ -305,9 +321,9 @@ release, follow the [Homebrew maintainer guide](https://github.com/lambdadb/lamb
 update checksums, pass installation checks and prepare a tap PR. Tap publication
 is separate from this repository's npm workflow; no cross-repository write or
 automatic tap update is configured. The public
-[LambdaDB tap](https://github.com/lambdadb/homebrew-tap) provides stable `0.1.1`
-(verified on 2026-10-04);
-installation evidence is recorded in [VALIDATION.md](VALIDATION.md#homebrew-publication).
+[LambdaDB tap](https://github.com/lambdadb/homebrew-tap) provides stable `0.1.2`
+(verified on 2026-10-04). Public installation and disposable-tap upgrade evidence
+is recorded in [VALIDATION.md](VALIDATION.md#cli-012-post-release-verification-2026-10-04).
 
 ## Design references
 

package/VALIDATION.md

@@ -3,8 +3,74 @@
 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`.
+  The completed tap handoff and bounded upgrade evidence are recorded below.
+
+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 post-release verification (2026-10-04)
+
+[PR #16](https://github.com/lambdadb/lambdadb-cli/pull/16) merged as
+`aefbaeed9c799e76dd7a9501ecda6ab80dc6e958`, preserving release commit `6628fe0`
+as an ancestor of develop and starting the 0.1.3-dev.1 development base.
+
+- [Automatic publication](https://github.com/lambdadb/lambdadb-cli/actions/runs/37192027479)
+  passed Node 22/24 validation and published 0.1.3-dev.13. An independent isolated
+  registry consumer passed all 46 CLI contracts, version/help, SDK 0.7.0 and
+  integrity checks. npm audit signatures verified four signatures and three
+  attestations. Decoded provenance matched the artifact digest, merge commit,
+  repository, develop ref and workflow run. At verification, dev=0.1.3-dev.13
+  and latest=0.1.2. Temporary consumer, source archive and cache were removed.
+- [Homebrew PR #6](https://github.com/lambdadb/homebrew-tap/pull/6) merged as
+  `ae9a7456acd10015d51b9ea8d58aee76afe3da28`. The public formula matches the
+  CLI-side formula and pins the verified npm 0.1.2 artifact and release lockfile.
+- [Public-tap CI](https://github.com/lambdadb/homebrew-tap/actions/runs/37192619208)
+  passed on macOS arm64 and Linux x86_64. It installed from the remote public tap
+  and checked formula equality, style, version, JSON configuration, file
+  permissions and Node runtime selection. Existing migration checks also passed;
+  no migration formula was changed. Hosted test installations and taps were removed.
+- A separate local macOS arm64 test installed 0.1.1 into a disposable tap, replaced
+  its formula with the exact merged public 0.1.2 formula, ran brew upgrade and
+  verified version 0.1.2 and brew test. Both test-owned versions and the temporary
+  tap were removed; the original user taps were preserved. This establishes the
+  formula version transition, not an existing user's public-tap upgrade or Linux
+  upgrade coverage. No LambdaDB service resources or credentials were used.
+- Merged feature branches were removed and both primary checkouts were clean.
+  The candidate and development-service evidence below remain historical samples;
+  this post-release verification did not run another live service smoke.
+
 ## CLI 0.1.2 stable candidate (2026-10-04)
 
+This section records the pre-publication candidate milestone. Publication and
+post-release results are recorded above.
+
 Prepared release/0.1.2 from reviewed develop merge `aef74a3`, retaining SDK 0.7.0
 and all reviewed runtime/test changes. The release branch changes only version
 metadata, the dated changelog and release/validation documentation. Stable npm

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-cli",
-  "version": "0.1.2",
+  "version": "0.1.3-dev.14",
   "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": "8e764223142f9e9655b85bb5057e1636b69aec29"
 }