chore: the home registry is The Source, never 'the forge' — sweep the misnomer out of the release rail, workflows, and release notes (Forge is a different product; the stored CI secret keeps its historical name)
This commit is contained in:
parent
c6c6ea6b57
commit
09352c2b37
4 changed files with 55 additions and 51 deletions
|
|
@ -70,8 +70,8 @@ to the caller today.
|
|||
pre-existing meaning). **Migration-grade exports set `includeHidden: true`** — a
|
||||
complete-canon export must carry every visibility tier; consumer-facing exports
|
||||
leave it off.
|
||||
- **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
|
||||
- **Ops note (consumer-invisible): the release pipeline's home-registry publish (The
|
||||
Source, source.soulcraft.com) 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.
|
||||
|
||||
## v9.0.0 — 2026-08-04 (the field-addressing law: your names and system.*, nothing in between)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue