@kungfu-tech/buildchain 2.4.1-alpha.0 → 2.4.1-alpha.1

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.
@@ -180,11 +180,16 @@ or ref finalization needs a later promotion run.
180
180
  After a publish transaction reaches `complete`, the action generates the unified
181
181
  `buildchain-release-passport` in `.buildchain/release-passport` by default and
182
182
  persists those files under `release-passport/` in the durable release-state ref.
183
+ Set `release-passport-product-name` to record the consumer product name, for
184
+ example `Libnode`, instead of the default `Buildchain`.
183
185
  When present, the passport includes the aggregate build summary, platform
184
186
  artifact manifests, npm publish evidence, dist-tag promotion evidence, the
185
187
  release-state ref, trusted publishing metadata, and the Buildchain transaction
186
- result. Set `release-passport: "false"` only for a controlled recovery run that
187
- must skip passport generation.
188
+ result. After the first passport upload, Buildchain backfills the durable
189
+ release-state SHA into `buildchain.release.json` and persists the passport
190
+ again, so the consumer-side passport is a complete audit entrypoint. Set
191
+ `release-passport: "false"` only for a controlled recovery run that must skip
192
+ passport generation.
188
193
 
189
194
  Finalization recovery is anchored to the durable transaction, not to a single
190
195
  workflow run SHA. After a generated version-state PR is merged, the current
@@ -156,7 +156,9 @@ the `release-passport/*` files into the durable `buildchain/release-state/...`
156
156
  ref. The passport is the stable release artifact for agents and people: it
157
157
  links the package set, npm publish evidence, dist-tag evidence, build summary,
158
158
  platform artifact manifests, trusted publishing metadata, release-state ref,
159
- and transaction result in one schema.
159
+ durable release-state SHA, and transaction result in one schema. Consumer
160
+ repositories can set `release-passport-product-name` so the passport names their
161
+ product instead of the Buildchain default.
160
162
 
161
163
  ## Evidence
162
164
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kungfu-tech/buildchain",
3
- "version": "2.4.1-alpha.0",
3
+ "version": "2.4.1-alpha.1",
4
4
  "private": false,
5
5
  "description": "Buildchain Release Passport, release governance, CLI toolkit, and site facts.",
6
6
  "repository": "https://github.com/kungfu-systems/buildchain",