@functional-systems/lambdadb-cli 0.1.1-dev.8 → 0.1.1-dev.9

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.
package/CHANGELOG.md CHANGED
@@ -16,6 +16,11 @@
16
16
  - Synchronize the 0.1.0 release history into develop and start the 0.1.1 development
17
17
  line. Stable installs use npm's default channel; dev builds remain opt-in.
18
18
 
19
+ ### Documentation
20
+
21
+ - Document the published stable npm channel, public Homebrew installation and
22
+ completed release verification on the default branch.
23
+
19
24
  ## [0.1.0] - 2026-09-19
20
25
 
21
26
  ### Added
package/RELEASING.md CHANGED
@@ -14,11 +14,12 @@ unqualified npm install passed all 35 CLI contracts, version/help, integrity,
14
14
  provenance and signature checks. Version/tag and attestation metadata propagated
15
15
  separately; verification used read retries without republishing.
16
16
 
17
- The post-release synchronization brings main history back into develop with
18
- `0.1.1-dev.1` as the next development base. Its promotion PR must preserve shared
19
- ancestry with a merge commit. Once merged, the normal develop push workflow
20
- publishes a numbered `0.1.1-dev.N` build on `dev`; it does not move `latest`.
21
- No separate stable release or tag is needed for this maintenance step.
17
+ The post-release synchronization merged main history back into develop with
18
+ `0.1.1-dev.1` as its development base. After the Homebrew documentation merge,
19
+ [develop CI](https://github.com/lambdadb/lambdadb-cli/actions/runs/35434313586)
20
+ published and verified `0.1.1-dev.8` from `225dec3` on 2026-09-19. Registry and
21
+ provenance metadata identify that commit; `latest` remains `0.1.0`. Development
22
+ builds do not require a separate stable release or tag.
22
23
 
23
24
  Bootstrap `0.1.0-dev.1` and the first OIDC development builds were verified on
24
25
  2026-09-18. The ordinary develop merge published `0.1.0-dev.5` in
@@ -254,7 +255,8 @@ Use existing known development tag/alias refs for additional live ref evidence.
254
255
 
255
256
  ## Homebrew handoff
256
257
 
257
- The stable formula is maintained in `packaging/homebrew/Formula/lambdadb-cli.rb`.
258
+ The stable formula is maintained on develop in
259
+ [`packaging/homebrew/Formula/lambdadb-cli.rb`](https://github.com/lambdadb/lambdadb-cli/blob/develop/packaging/homebrew/Formula/lambdadb-cli.rb).
258
260
  It consumes the verified npm artifact and the lockfile from its immutable release
259
261
  commit. Development publication does not update Homebrew. After each stable npm
260
262
  release, follow the [Homebrew maintainer guide](https://github.com/lambdadb/lambdadb-cli/tree/develop/packaging/homebrew#readme) to
package/VALIDATION.md CHANGED
@@ -3,6 +3,21 @@
3
3
  Updated: 2026-09-19. Local contract tests use loopback servers and synthetic
4
4
  credentials. A separate authenticated development-project smoke is recorded below.
5
5
 
6
+ ## Development publication after Homebrew documentation
7
+
8
+ On 2026-09-19, the [develop push workflow](https://github.com/lambdadb/lambdadb-cli/actions/runs/35434313586)
9
+ completed successfully for `225dec37f48dd5603af7fe777c1eb24d9041188c`, the merge of
10
+ PR #8. Node 22/24 validation and tests of the exact publication tarball passed.
11
+ The publish job accepted `0.1.1-dev.8`, retried registry reads during propagation,
12
+ and finished with `result=published` without repeating the write.
13
+
14
+ Subsequent read-only registry checks confirmed `dev=0.1.1-dev.8`,
15
+ `latest=0.1.0`, and the package's `gitHead` matching the merge commit. Decoded
16
+ provenance metadata identifies that same commit, `refs/heads/develop`,
17
+ `.github/workflows/publish.yaml` and workflow attempt 1; its subject digest matches
18
+ registry integrity. This metadata inspection did not repeat signature verification,
19
+ a consumer installation or the LambdaDB live smoke.
20
+
6
21
  ## Homebrew publication
7
22
 
8
23
  On 2026-09-19, the public
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@functional-systems/lambdadb-cli",
3
- "version": "0.1.1-dev.8",
3
+ "version": "0.1.1-dev.9",
4
4
  "private": false,
5
5
  "description": "Project-scoped LambdaDB command-line tools",
6
6
  "type": "module",
@@ -53,5 +53,5 @@
53
53
  "url": "https://github.com/lambdadb/lambdadb-cli/issues"
54
54
  },
55
55
  "license": "Apache-2.0",
56
- "gitHead": "225dec37f48dd5603af7fe777c1eb24d9041188c"
56
+ "gitHead": "513af6e4d262edd380013c86d51a20aad16274d7"
57
57
  }