Fix CI
Release rolling / release (push) Successful in 7m10s

This commit is contained in:
Raven Scott
2026-07-31 11:52:26 -04:00
parent 2b7025b22d
commit cdf776a68f
3 changed files with 24 additions and 23 deletions
+10 -2
View File
@@ -61,16 +61,24 @@ pear install pear://khtauzttriz8dpgrphj79rfy98iwoatqm59fnogtsdqk5f1kg6ao
Packaged binaries embed **`pear-runtime`**. Disable with `--no-updates` or `BARE_OS_OTA_DISABLE=1`.
CI stages `by-arch/` with **`pear-ci`** using secret **`PEAR_PRIMARY_KEY`** (64-char hex). Snapshots live in `ci/snapshot-seeder.json` and `ci/snapshot-booter.json`.
CI publishes **`by-arch-*.tar.gz`** on the rolling release but does **not** pear-ci stage. Stage offline:
```bash
# after npm run make (or unpack by-arch trees from rolling)
PEAR_PRIMARY_KEY=<64-hex> bash scripts/pear-stage-by-arch.sh
```
Snapshots (when staging): `ci/snapshot-seeder.json`, `ci/snapshot-booter.json`.
## Secrets
| Secret | Role |
|--------|------|
| `RELEASE_TOKEN` | Gitea release write for tag `rolling` |
| `PEAR_PRIMARY_KEY` | pear-ci Corestore identity |
| `GITEA_URL` | Optional forge base URL |
`PEAR_PRIMARY_KEY` is only for **offline** `scripts/pear-stage-by-arch.sh`, not CI.
## Related
- Legacy channel notes: [PEAR-RUN.md](PEAR-RUN.md)