feat(release): the forge publish leg moves to CI on the tag push; the laptop verifies by readback and keeps the abort-before-storefront guard
This commit is contained in:
parent
4d196af41b
commit
3e4a17dcdf
3 changed files with 94 additions and 21 deletions
|
|
@ -61,6 +61,9 @@ to the caller today.
|
|||
Migration-audit evidence, not a repair: nonzero drift is reported loudly
|
||||
(`console.warn` with the counts) and nothing is auto-healed — run `brain.repairIndex()`
|
||||
to reconcile the metadata index once drift is confirmed.
|
||||
- **Ops note (consumer-invisible): the release pipeline's forge-registry publish now runs
|
||||
on CI**, triggered by the release tag, instead of PUTting the tarball from the laptop
|
||||
over WAN — no change to what gets published or how a consumer installs it.
|
||||
|
||||
## v8.10.1 — 2026-07-24 (the no-hot-retry contract + warm()'s metadata surface under native providers)
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue