@kungfu-tech/buildchain 2.8.9 → 2.8.10-alpha.0

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.
@@ -419,8 +419,11 @@ status checks are satisfied by machine-verifiable Buildchain evidence rather
419
419
  than a human PR. The protected ref PATCH itself uses the generated ref update
420
420
  token; the reusable wrapper defaults it to
421
421
  `secrets.BUILDCHAIN_PROMOTION_TOKEN || github.token`. If direct generated
422
- bookkeeping is still rejected, Buildchain fails with a token/protection
423
- diagnostic instead of creating a post-publish PR.
422
+ release finalization bookkeeping is still rejected, Buildchain creates or
423
+ reuses a same-repository `buildchain/version-state/*` PR based on the current
424
+ target channel head and records `finalization-needed=true` in the durable
425
+ transaction output. Strict alpha bookkeeping still fails with a
426
+ token/protection diagnostic instead of creating a post-publish PR.
424
427
  Buildchain's own promotion workflow reads `BUILDCHAIN_PROMOTION_BYPASS_APPS`,
425
428
  `BUILDCHAIN_PROMOTION_BYPASS_USERS`, and
426
429
  `BUILDCHAIN_PROMOTION_BYPASS_TEAMS` repository variables so the declared bypass
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kungfu-tech/buildchain",
3
- "version": "2.8.9",
3
+ "version": "2.8.10-alpha.0",
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",