seed-release: tag + Forgejo Release per merged seed; auto-link the package #129

Merged

plat merged 1 commit from feat/seed-release into main

2026-08-15 19:07:41 +00:00

trevato commented

2026-08-15 18:31:42 +00:00

Owner

The human half of seed history (packages are the machine half). On a main push touching genesis/seed.tar.gz — i.e. exactly when a gate-validated reseed merges:

Tag seed-r<N> (run number parsed from the reseed merge message, seedVersion fallback) and create a Forgejo Release with seed.tar.gz + manifest.yaml attached and the manifest's repo refs in the body — the Releases tab becomes the browsable catalog of every seed that ever became genesis, pinned to the exact git state.
Auto-link the seed generic package to this repo (idempotent, PLAT_PAT) so it appears on the repo's Packages tab instead of only under the plat user's package space — fixes the "I don't see the seed in packages" discoverability gap.

Attachments and linking are best-effort with loud warnings ([attachment] MAX_SIZE etc.); the package registry remains the always-works fetch path for resolve_seed. Only merged, coldstart-gated seeds get a release — build-time candidate packages never do.

Companion to #125 (auto-triggers) and #127 (publish + resolution). Uses the existing PLAT_PAT secret; no other setup. First run fires when the r278 reseed PR merges.

🤖 Generated with Claude Code

The human half of seed history (packages are the machine half). On a `main` push touching `genesis/seed.tar.gz` — i.e. exactly when a gate-validated reseed merges: 1. **Tag `seed-r<N>`** (run number parsed from the reseed merge message, `seedVersion` fallback) and create a **Forgejo Release** with `seed.tar.gz` + `manifest.yaml` attached and the manifest's repo refs in the body — the Releases tab becomes the browsable catalog of every seed that ever became genesis, pinned to the exact git state. 2. **Auto-link the `seed` generic package to this repo** (idempotent, `PLAT_PAT`) so it appears on the repo's Packages tab instead of only under the plat user's package space — fixes the "I don't see the seed in packages" discoverability gap. Attachments and linking are best-effort with loud warnings (`[attachment] MAX_SIZE` etc.); the package registry remains the always-works fetch path for `resolve_seed`. Only merged, coldstart-gated seeds get a release — build-time candidate packages never do. Companion to #125 (auto-triggers) and #127 (publish + resolution). Uses the existing `PLAT_PAT` secret; no other setup. First run fires when the `r278` reseed PR merges. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

trevato added 1 commit

2026-08-15 18:31:42 +00:00

seed-release: tag + Forgejo Release per merged seed; auto-link the package

guard-ppt / no-ppt (push) Successful in 9s

Details

guard-ppt / no-ppt (pull_request) Successful in 10s

Details

688a1ad400

The human half of seed history: on a main push touching
genesis/seed.tar.gz (a gate-validated reseed merging), tag seed-r<N>,
create a Release with the tarball + manifest attached, and link the
generic seed package to this repo so it shows on the repo Packages tab.
Attachments and linking are best-effort with loud warnings; the package
registry remains the always-works path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>