Public: anyone can read this; nobody can change it.

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

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

The human half of seed history (packages are the machine half). On a main push touching genesis/seed.tar.gz — i.e.

Notes

shipped merged

opened this view on origin

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

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs